Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ceb7db8c2fa8d573efe822be6f46b07cb1320d23a7dfb78a70a16252e1dce1

Tx prefix hash: 15be18a1a49dea994874d87e193fa94673f31e8e2c2a3e939f5d3cb5df2424fd
Tx public key: 9dcab69a760be3d4430fcd6c50d4f2c928133400b2a801ba9df6ce06940cb1ab
Timestamp: 1685417741 Timestamp [UCT]: 2023-05-30 03:35:41 Age [y:d:h:m:s]: 01:170:07:48:38
Block: 771106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383105 RingCT/type: yes/0
Extra: 019dcab69a760be3d4430fcd6c50d4f2c928133400b2a801ba9df6ce06940cb1ab02110000000633af99f4000000000000000000

1 output(s) for total of 1.710038518000 dcy

stealth address amount amount idx
00: dba994cbd090651503a18593910cfb255ee0c1bc4b892468f1290bcb519a785c 1.710038518000 1220451 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": 771116, "vin": [ { "gen": { "height": 771106 } } ], "vout": [ { "amount": 1710038518, "target": { "key": "dba994cbd090651503a18593910cfb255ee0c1bc4b892468f1290bcb519a785c" } } ], "extra": [ 1, 157, 202, 182, 154, 118, 11, 227, 212, 67, 15, 205, 108, 80, 212, 242, 201, 40, 19, 52, 0, 178, 168, 1, 186, 157, 246, 206, 6, 148, 12, 177, 171, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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