Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cd9a39022cf72e75910b58d2ca918838bbb13ec58642766cdc9546031d71b70

Tx prefix hash: a32cff26d896d13bef48acf84a718840c7692d890468fd22b064eab4639f11b7
Tx public key: 6dab9f5ec08e90b2d47e309605d6e314f313a7b4d54a622c9014bfbe0a4bdd9f
Timestamp: 1703637079 Timestamp [UCT]: 2023-12-27 00:31:19 Age [y:d:h:m:s]: 01:108:01:09:01
Block: 921895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338332 RingCT/type: yes/0
Extra: 016dab9f5ec08e90b2d47e309605d6e314f313a7b4d54a622c9014bfbe0a4bdd9f0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dca07051868732ac361313bb4d6b38a379e4bc1f84044f18d314f21292c0985 0.600000000000 1379589 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": 921905, "vin": [ { "gen": { "height": 921895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dca07051868732ac361313bb4d6b38a379e4bc1f84044f18d314f21292c0985" } } ], "extra": [ 1, 109, 171, 159, 94, 192, 142, 144, 178, 212, 126, 48, 150, 5, 214, 227, 20, 243, 19, 167, 180, 213, 74, 98, 44, 144, 20, 191, 190, 10, 75, 221, 159, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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