Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83f1afd3bac453540cb655f8ef5bf548c3252c1ce91fc33a948c627f72d567aa

Tx prefix hash: e67d091cb7f17704e3c9a21e179b95263cac42fbf0b1ee1d49c607d6f4c828e5
Tx public key: 9a73a198233a838265777e1a998796cc7d7ea011cbbd210ea7e4b670afaf26dd
Timestamp: 1713440454 Timestamp [UCT]: 2024-04-18 11:40:54 Age [y:d:h:m:s]: 00:350:05:12:02
Block: 1003159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250373 RingCT/type: yes/0
Extra: 019a73a198233a838265777e1a998796cc7d7ea011cbbd210ea7e4b670afaf26dd02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acd6be21d02752192880c67dccf5e0e1beefa64c16b8dfb5e63a180e4dfda837 0.600000000000 1463689 of 15

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": 1003169, "vin": [ { "gen": { "height": 1003159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acd6be21d02752192880c67dccf5e0e1beefa64c16b8dfb5e63a180e4dfda837" } } ], "extra": [ 1, 154, 115, 161, 152, 35, 58, 131, 130, 101, 119, 126, 26, 153, 135, 150, 204, 125, 126, 160, 17, 203, 189, 33, 14, 167, 228, 182, 112, 175, 175, 38, 221, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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