Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 043484c0c946fa60ec6f957d06b396aa648b4a427b089882342b00d43d400360

Tx prefix hash: e6cf5cba579c4480e1f4b9c9bddf77930441e38647eea05bb7d031629c7b5c55
Tx public key: 619c2921e7578cf97517ede0ba0ee986e110d61ed364ad293b6b0dc0873a9ab4
Timestamp: 1717363253 Timestamp [UCT]: 2024-06-02 21:20:53 Age [y:d:h:m:s]: 01:159:22:20:00
Block: 1035703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372880 RingCT/type: yes/0
Extra: 01619c2921e7578cf97517ede0ba0ee986e110d61ed364ad293b6b0dc0873a9ab4021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15209a3cd11ae43dedd4aacf1e7f8c6f3eca8170eb676fc1f071d9ff6215aebc 0.600000000000 1504226 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": 1035713, "vin": [ { "gen": { "height": 1035703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15209a3cd11ae43dedd4aacf1e7f8c6f3eca8170eb676fc1f071d9ff6215aebc" } } ], "extra": [ 1, 97, 156, 41, 33, 231, 87, 140, 249, 117, 23, 237, 224, 186, 14, 233, 134, 225, 16, 214, 30, 211, 100, 173, 41, 59, 107, 13, 192, 135, 58, 154, 180, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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