Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3ea15fb61867dbe8c17ead8d6493ffb46f60a4d370983d4603bc8f1a775aaff

Tx prefix hash: 21b80e83a856b917b72aa1b4c1c09e0cc0e7724d7442133320698cb25ad879ea
Tx public key: ad779c9a1bb1e2ad11a5dc8f78b797390c88859242046442c1919421fc0f3bc9
Timestamp: 1677641813 Timestamp [UCT]: 2023-03-01 03:36:53 Age [y:d:h:m:s]: 02:049:00:27:27
Block: 707264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556622 RingCT/type: yes/0
Extra: 01ad779c9a1bb1e2ad11a5dc8f78b797390c88859242046442c1919421fc0f3bc902110000000383600029000000000000000000

1 output(s) for total of 2.783176004000 dcy

stealth address amount amount idx
00: 7bd52a63d3be0c4dd978f101afcd5b64d3122c575d367d2f5d42c0ead59cc319 2.783176004000 1151063 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": 707274, "vin": [ { "gen": { "height": 707264 } } ], "vout": [ { "amount": 2783176004, "target": { "key": "7bd52a63d3be0c4dd978f101afcd5b64d3122c575d367d2f5d42c0ead59cc319" } } ], "extra": [ 1, 173, 119, 156, 154, 27, 177, 226, 173, 17, 165, 220, 143, 120, 183, 151, 57, 12, 136, 133, 146, 66, 4, 100, 66, 193, 145, 148, 33, 252, 15, 59, 201, 2, 17, 0, 0, 0, 3, 131, 96, 0, 41, 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