Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebdf4084e2f59da0de5a802975c89fc9c4daa73e5fcd61832be552fa87a67b5c

Tx prefix hash: df47c592ce84b2cd7f57f7001bbf0ca67b3810fbe15c6c5feaf71a3274b3d802
Tx public key: 4fff371723a0d1ec5c0f956e42601850fb2783ac0fb805150b4d1989b1ab8d46
Timestamp: 1737231679 Timestamp [UCT]: 2025-01-18 20:21:19 Age [y:d:h:m:s]: 00:336:09:54:31
Block: 1200224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238034 RingCT/type: yes/0
Extra: 014fff371723a0d1ec5c0f956e42601850fb2783ac0fb805150b4d1989b1ab8d460211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fb8fa934dc78ca3907f6f29477b0fd1755cf07cfabe051440445686b29f6535 0.600000000000 1686867 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": 1200234, "vin": [ { "gen": { "height": 1200224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fb8fa934dc78ca3907f6f29477b0fd1755cf07cfabe051440445686b29f6535" } } ], "extra": [ 1, 79, 255, 55, 23, 35, 160, 209, 236, 92, 15, 149, 110, 66, 96, 24, 80, 251, 39, 131, 172, 15, 184, 5, 21, 11, 77, 25, 137, 177, 171, 141, 70, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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