Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4600f5acabb80dca8e2b6d55fd13b2413a8cd358f97fdfe93b3170581d12adf

Tx prefix hash: d1224e2f0839d093f42d9f9a782b932a44ca7bbe049ab74aa60844597a4bba3c
Tx public key: 0d522ce3e28541aed928c3d292779a029cd85edfe34ba4b248f48ba78a4cc0a3
Timestamp: 1723862965 Timestamp [UCT]: 2024-08-17 02:49:25 Age [y:d:h:m:s]: 01:082:10:11:10
Block: 1089582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317364 RingCT/type: yes/0
Extra: 010d522ce3e28541aed928c3d292779a029cd85edfe34ba4b248f48ba78a4cc0a3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93616e2801930822e3d530d6f85768276ce6146b914f1a8137749e98e47f06bc 0.600000000000 1564205 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": 1089592, "vin": [ { "gen": { "height": 1089582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93616e2801930822e3d530d6f85768276ce6146b914f1a8137749e98e47f06bc" } } ], "extra": [ 1, 13, 82, 44, 227, 226, 133, 65, 174, 217, 40, 195, 210, 146, 119, 154, 2, 156, 216, 94, 223, 227, 75, 164, 178, 72, 244, 139, 167, 138, 76, 192, 163, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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