Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0206edf200d42a2bc6a16fd794ebab0607bbb14ad11146496172b9bf20557ce2

Tx prefix hash: 9652724692f965b26b4af3a3a43d4c746e465e044f4d0a39d3d4a37f388cd9e4
Tx public key: eddfca99dfafb3d1b4428a6343b6bdc24ba305dc32629889c324bbe708bd01e6
Timestamp: 1699678577 Timestamp [UCT]: 2023-11-11 04:56:17 Age [y:d:h:m:s]: 01:151:01:55:50
Block: 889084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369167 RingCT/type: yes/0
Extra: 01eddfca99dfafb3d1b4428a6343b6bdc24ba305dc32629889c324bbe708bd01e602110000000433af99f4000000000000000000

1 output(s) for total of 0.695177378000 dcy

stealth address amount amount idx
00: 7e5fb7d7e2ad5d1789355e1a9d91fc58893cd859141a8dfae8b10c8d31f04184 0.695177378000 1345061 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": 889094, "vin": [ { "gen": { "height": 889084 } } ], "vout": [ { "amount": 695177378, "target": { "key": "7e5fb7d7e2ad5d1789355e1a9d91fc58893cd859141a8dfae8b10c8d31f04184" } } ], "extra": [ 1, 237, 223, 202, 153, 223, 175, 179, 209, 180, 66, 138, 99, 67, 182, 189, 194, 75, 163, 5, 220, 50, 98, 152, 137, 195, 36, 187, 231, 8, 189, 1, 230, 2, 17, 0, 0, 0, 4, 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