Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec054ba2fbfea6f6683461bae1ee960a47a317047fa3a54477f21a34bbecd9bd

Tx prefix hash: 2bd42e748b99ca5886c5aebc759250a7feb0d1d281d108a6424a4d8ff476de3e
Tx public key: 01e619674366be084fdfc6d70606d9350c93ff74dd2fa6e53ef782dffff7c2e6
Timestamp: 1742127432 Timestamp [UCT]: 2025-03-16 12:17:12 Age [y:d:h:m:s]: 00:298:02:17:23
Block: 1240551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210844 RingCT/type: yes/0
Extra: 0101e619674366be084fdfc6d70606d9350c93ff74dd2fa6e53ef782dffff7c2e602110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 938c5447752e19b9c2ef7854ea166752f155d4c65691fe0688e9fb5f8b9baa1c 0.600000000000 1727524 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": 1240561, "vin": [ { "gen": { "height": 1240551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "938c5447752e19b9c2ef7854ea166752f155d4c65691fe0688e9fb5f8b9baa1c" } } ], "extra": [ 1, 1, 230, 25, 103, 67, 102, 190, 8, 79, 223, 198, 215, 6, 6, 217, 53, 12, 147, 255, 116, 221, 47, 166, 229, 62, 247, 130, 223, 255, 247, 194, 230, 2, 17, 0, 0, 0, 13, 0, 127, 151, 138, 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