Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ba7bbe6c08c0d91638e39e711f090ac5d5be01b5a96846770e457fb3d7ed3fe

Tx prefix hash: 416324af907bdca291c2f7d049555af050aa0e8f6eb469c7469b396e65fbfc5e
Tx public key: 9af048ccac528a9850fe06ba0eb1b16c0d26b40026e87431500bc085164150df
Timestamp: 1650654307 Timestamp [UCT]: 2022-04-22 19:05:07 Age [y:d:h:m:s]: 02:013:13:39:05
Block: 485859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529414 RingCT/type: yes/0
Extra: 019af048ccac528a9850fe06ba0eb1b16c0d26b40026e87431500bc085164150df021100000001bf7ee4e7000000000000000000

1 output(s) for total of 15.071194324000 dcy

stealth address amount amount idx
00: 2906fa3aaf0c69fee00c879bb1f60101b2d1ee666b95b9c54367d89f331630f7 15.071194324000 908032 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": 485869, "vin": [ { "gen": { "height": 485859 } } ], "vout": [ { "amount": 15071194324, "target": { "key": "2906fa3aaf0c69fee00c879bb1f60101b2d1ee666b95b9c54367d89f331630f7" } } ], "extra": [ 1, 154, 240, 72, 204, 172, 82, 138, 152, 80, 254, 6, 186, 14, 177, 177, 108, 13, 38, 180, 0, 38, 232, 116, 49, 80, 11, 192, 133, 22, 65, 80, 223, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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