Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d45000114334e725de874b60084b05e47830823ab4b9aa51b258a128cc8b14fa

Tx prefix hash: 9626ae7f795833c2fee219ff20b660fcda40bf1c7abb42a113d9f83b13a7a6a0
Tx public key: 57b7e23ceae727652c2a9a11c76253e8bc4c8e92127a95b1808afffec946f40d
Timestamp: 1725282624 Timestamp [UCT]: 2024-09-02 13:10:24 Age [y:d:h:m:s]: 00:269:03:26:44
Block: 1101344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192260 RingCT/type: yes/0
Extra: 0157b7e23ceae727652c2a9a11c76253e8bc4c8e92127a95b1808afffec946f40d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aabc9a7884e92790168c594ca7d7e316da3313c7dfb9e6252a6e2c5a4c02782 0.600000000000 1577361 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": 1101354, "vin": [ { "gen": { "height": 1101344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aabc9a7884e92790168c594ca7d7e316da3313c7dfb9e6252a6e2c5a4c02782" } } ], "extra": [ 1, 87, 183, 226, 60, 234, 231, 39, 101, 44, 42, 154, 17, 199, 98, 83, 232, 188, 76, 142, 146, 18, 122, 149, 177, 128, 138, 255, 254, 201, 70, 244, 13, 2, 17, 0, 0, 0, 5, 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