Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7801a752e4d567576deac05017bb946aea8ea378cf9ddae402f8453e531d626

Tx prefix hash: 9cc50e040fb6b2a31519972330b1a6b3069ffb6899fc48940042cbd3fc558077
Tx public key: a271924091b44a648c11c9241c2278aede0150ed80b4a3a29205ab6ab4227d9e
Timestamp: 1636580647 Timestamp [UCT]: 2021-11-10 21:44:07 Age [y:d:h:m:s]: 03:122:20:30:47
Block: 371659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 866200 RingCT/type: yes/0
Extra: 01a271924091b44a648c11c9241c2278aede0150ed80b4a3a29205ab6ab4227d9e0211000000014a0f5013000000000000000000

1 output(s) for total of 36.019679308000 dcy

stealth address amount amount idx
00: e10e56bfa5f9819fb7a14f3652dd0a6b74e2dc527272ff1939392a1ebc4d9713 36.019679308000 753099 of 0

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": 371669, "vin": [ { "gen": { "height": 371659 } } ], "vout": [ { "amount": 36019679308, "target": { "key": "e10e56bfa5f9819fb7a14f3652dd0a6b74e2dc527272ff1939392a1ebc4d9713" } } ], "extra": [ 1, 162, 113, 146, 64, 145, 180, 74, 100, 140, 17, 201, 36, 28, 34, 120, 174, 222, 1, 80, 237, 128, 180, 163, 162, 146, 5, 171, 106, 180, 34, 125, 158, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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