Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad2c682ac8de54b4932b5c78581dbc4fc1f34f2d64e38ebfbc985603c7c65fb8

Tx prefix hash: e5a49613dda06b3382a0337f27ce166cf169125d0fba01520afb54e4b00acf2b
Tx public key: 39c0baa951881064b8b3a4e823c3152be5c42637079dcfc89f0060df719d15e4
Timestamp: 1716733500 Timestamp [UCT]: 2024-05-26 14:25:00 Age [y:d:h:m:s]: 01:022:04:50:06
Block: 1030488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276661 RingCT/type: yes/0
Extra: 0139c0baa951881064b8b3a4e823c3152be5c42637079dcfc89f0060df719d15e40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d08c84c3e568f4bd768e376f521840f235992598ed61e087bf75e87816892e3f 0.600000000000 1498743 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": 1030498, "vin": [ { "gen": { "height": 1030488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d08c84c3e568f4bd768e376f521840f235992598ed61e087bf75e87816892e3f" } } ], "extra": [ 1, 57, 192, 186, 169, 81, 136, 16, 100, 184, 179, 164, 232, 35, 195, 21, 43, 229, 196, 38, 55, 7, 157, 207, 200, 159, 0, 96, 223, 113, 157, 21, 228, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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