Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59011fb9e899ffcc52bae97e15bb1a36965a22f36784c4c86411ef7f3f382ac2

Tx prefix hash: 778b3ea8f365291e2a932dbe7d0fcf742849c0e7c12db042971fa7397c924d0d
Tx public key: 5757406f47d716d4e0f7e606895434373803f3b71e5fe55a96b4593e7044ad95
Timestamp: 1701896110 Timestamp [UCT]: 2023-12-06 20:55:10 Age [y:d:h:m:s]: 01:362:08:49:37
Block: 907461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517885 RingCT/type: yes/0
Extra: 015757406f47d716d4e0f7e606895434373803f3b71e5fe55a96b4593e7044ad95021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.604233743000 dcy

stealth address amount amount idx
00: 332bef655b4492284b4fc62b8735cd026856854812478f959c31c80e3741f6c0 0.604233743000 1364450 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": 907471, "vin": [ { "gen": { "height": 907461 } } ], "vout": [ { "amount": 604233743, "target": { "key": "332bef655b4492284b4fc62b8735cd026856854812478f959c31c80e3741f6c0" } } ], "extra": [ 1, 87, 87, 64, 111, 71, 215, 22, 212, 224, 247, 230, 6, 137, 84, 52, 55, 56, 3, 243, 183, 30, 95, 229, 90, 150, 180, 89, 62, 112, 68, 173, 149, 2, 17, 0, 0, 0, 5, 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