Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 18f0298af8b867598ca6a1753d935073afc7b5bb11c16c11cfbe05067e689744

Tx prefix hash: b600cca5dcca37edaf447ef0b8a24526fc3c55fc4bc1d9c031f4b5ee74859f6d
Tx public key: 72612b5f2fba487b4cb076815571e8c8f762eea71cb2f0e571f3d5608063ef26
Timestamp: 1706961258 Timestamp [UCT]: 2024-02-03 11:54:18 Age [y:d:h:m:s]: 00:347:11:03:40
Block: 949449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248742 RingCT/type: yes/0
Extra: 0172612b5f2fba487b4cb076815571e8c8f762eea71cb2f0e571f3d5608063ef2602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0a5bd15839cdfd02cd3aae2d758c436e335d329825919f1a2eb290d9abb1691 0.600000000000 1407975 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 949459, "vin": [ { "gen": { "height": 949449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0a5bd15839cdfd02cd3aae2d758c436e335d329825919f1a2eb290d9abb1691" } } ], "extra": [ 1, 114, 97, 43, 95, 47, 186, 72, 123, 76, 176, 118, 129, 85, 113, 232, 200, 247, 98, 238, 167, 28, 178, 240, 229, 113, 243, 213, 96, 128, 99, 239, 38, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8