Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08b1a6188bccc395129d08d69d399cd69a30ea635796e2c9ff2a1e782ddc4035

Tx prefix hash: 114ef5624945b4051f77f7bccfd3b12606eeff612f698a1606bafd609d1fdee1
Tx public key: 47260277896d70376bbfbfc30cf26e5d30f871db2b4c5d4dc26d56fefe4c43fb
Timestamp: 1742253063 Timestamp [UCT]: 2025-03-17 23:11:03 Age [y:d:h:m:s]: 00:248:02:28:34
Block: 1241585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175033 RingCT/type: yes/0
Extra: 0147260277896d70376bbfbfc30cf26e5d30f871db2b4c5d4dc26d56fefe4c43fb0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a02412c9212f2fe5425262310e6bf9241c957f5ecaa2077582c324ddd35b1fa 0.600000000000 1728558 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": 1241595, "vin": [ { "gen": { "height": 1241585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a02412c9212f2fe5425262310e6bf9241c957f5ecaa2077582c324ddd35b1fa" } } ], "extra": [ 1, 71, 38, 2, 119, 137, 109, 112, 55, 107, 191, 191, 195, 12, 242, 110, 93, 48, 248, 113, 219, 43, 76, 93, 77, 194, 109, 86, 254, 254, 76, 67, 251, 2, 17, 0, 0, 0, 5, 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