Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10b8f6b428a54a5b5e5931074e8fabe86e34588e0563724945aee3d4471e5660

Tx prefix hash: 3a45101072e7ca4ab1a0ff5696e7257d4bb716274c49f991feac3b2218d5dd65
Tx public key: 685759d69fa4250e20248013f8a2e8aa83b6e156849d436d8d7cc07a90d240f6
Timestamp: 1721368473 Timestamp [UCT]: 2024-07-19 05:54:33 Age [y:d:h:m:s]: 01:081:08:17:57
Block: 1068917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316580 RingCT/type: yes/0
Extra: 01685759d69fa4250e20248013f8a2e8aa83b6e156849d436d8d7cc07a90d240f602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 755fd843bb86dd3539207bd50f5ac877c99e8aa7246e52feba1c60e0a4dc845c 0.600000000000 1540136 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": 1068927, "vin": [ { "gen": { "height": 1068917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "755fd843bb86dd3539207bd50f5ac877c99e8aa7246e52feba1c60e0a4dc845c" } } ], "extra": [ 1, 104, 87, 89, 214, 159, 164, 37, 14, 32, 36, 128, 19, 248, 162, 232, 170, 131, 182, 225, 86, 132, 157, 67, 109, 141, 124, 192, 122, 144, 210, 64, 246, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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