Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8da5cae3accd8a33fadb19f8c0e27c48cebcc7c5028d352a9c9421392e1c64c6

Tx prefix hash: e534c1bf2cf9fb4d4fc1a4cc347dfa619f0389832c89a43a9c5f58ec23b881cd
Tx public key: e95f322ee1376b5d352ffc1b6296a70e8cee6f0ebebccad33320055742513227
Timestamp: 1719014909 Timestamp [UCT]: 2024-06-22 00:08:29 Age [y:d:h:m:s]: 00:286:13:50:54
Block: 1049373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204795 RingCT/type: yes/0
Extra: 01e95f322ee1376b5d352ffc1b6296a70e8cee6f0ebebccad3332005574251322702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec2aa1e4d1158efb4eef18036f80c69fbc8d3f86acfb7c97211f2940a4bf2026 0.600000000000 1519472 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": 1049383, "vin": [ { "gen": { "height": 1049373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec2aa1e4d1158efb4eef18036f80c69fbc8d3f86acfb7c97211f2940a4bf2026" } } ], "extra": [ 1, 233, 95, 50, 46, 225, 55, 107, 93, 53, 47, 252, 27, 98, 150, 167, 14, 140, 238, 111, 14, 190, 188, 202, 211, 51, 32, 5, 87, 66, 81, 50, 39, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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