Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9b703a0978e97f5ad9e6be02209980f2ef906b8354663354db7010a6465811f

Tx prefix hash: 19b2cffb3e51a9c46343a458829a5b606c3df95ef0f1980c6a56629018789455
Tx public key: 200b0f894ee5aa734a332ccfc4e5481d1e071386c0c4e495d12183d3015a2713
Timestamp: 1700083163 Timestamp [UCT]: 2023-11-15 21:19:23 Age [y:d:h:m:s]: 01:200:03:03:55
Block: 892434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404256 RingCT/type: yes/0
Extra: 01200b0f894ee5aa734a332ccfc4e5481d1e071386c0c4e495d12183d3015a2713021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.677634776000 dcy

stealth address amount amount idx
00: e1a12f0a2983d30d08fad512b44a614ca974241298bd6584f14d34d775246bf5 0.677634776000 1348553 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": 892444, "vin": [ { "gen": { "height": 892434 } } ], "vout": [ { "amount": 677634776, "target": { "key": "e1a12f0a2983d30d08fad512b44a614ca974241298bd6584f14d34d775246bf5" } } ], "extra": [ 1, 32, 11, 15, 137, 78, 229, 170, 115, 74, 51, 44, 207, 196, 229, 72, 29, 30, 7, 19, 134, 192, 196, 228, 149, 209, 33, 131, 211, 1, 90, 39, 19, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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