Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4516bd9c64c06d7ffe4f4a8b6f20351bf941dadc7d7393cd2feda631cad95ce1

Tx prefix hash: 78634bc0aa4f19d91adad6201994570f3424da64f8a83b30cd9635692c95813d
Tx public key: b6140a96dd994637d0e1a3e51ddc83e5e340e18ef8a74aea18a1a00a04453202
Timestamp: 1758969996 Timestamp [UCT]: 2025-09-27 10:46:36 Age [y:d:h:m:s]: 00:086:18:50:31
Block: 1377514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62143 RingCT/type: yes/0
Extra: 01b6140a96dd994637d0e1a3e51ddc83e5e340e18ef8a74aea18a1a00a04453202021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e66f66d8d96ef3b9202da94f1aaa7a33622c196ceeb0bc2f5715053a01bc32c3 0.600000000000 1865609 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": 1377524, "vin": [ { "gen": { "height": 1377514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e66f66d8d96ef3b9202da94f1aaa7a33622c196ceeb0bc2f5715053a01bc32c3" } } ], "extra": [ 1, 182, 20, 10, 150, 221, 153, 70, 55, 208, 225, 163, 229, 29, 220, 131, 229, 227, 64, 225, 142, 248, 167, 74, 234, 24, 161, 160, 10, 4, 69, 50, 2, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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