Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a87b43f4169d1fd69604fbfc925a088078201a1ef205c9cc057aa31aa7e093eb

Tx prefix hash: 240d89612c630f3853339284d6de95757a27eb1070b0495d2633cb77260afb0a
Tx public key: 924aadd95aa1e0a75752cda8d314e4af1a7fdc4d0c59bda7e8e16f4299c35217
Timestamp: 1659648523 Timestamp [UCT]: 2022-08-04 21:28:43 Age [y:d:h:m:s]: 02:303:05:22:28
Block: 558795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737976 RingCT/type: yes/0
Extra: 01924aadd95aa1e0a75752cda8d314e4af1a7fdc4d0c59bda7e8e16f4299c35217021100000008e6d27f9c000000000000000000

1 output(s) for total of 8.639335059000 dcy

stealth address amount amount idx
00: e53b9789e8e90002aa9c877378f5fdb7ebb76f52ef1e8e1b444bc00925494838 8.639335059000 990893 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": 558805, "vin": [ { "gen": { "height": 558795 } } ], "vout": [ { "amount": 8639335059, "target": { "key": "e53b9789e8e90002aa9c877378f5fdb7ebb76f52ef1e8e1b444bc00925494838" } } ], "extra": [ 1, 146, 74, 173, 217, 90, 161, 224, 167, 87, 82, 205, 168, 211, 20, 228, 175, 26, 127, 220, 77, 12, 89, 189, 167, 232, 225, 111, 66, 153, 195, 82, 23, 2, 17, 0, 0, 0, 8, 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