Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af07b6cd1a164fc2300a73f2703c79abd974278d9a5d53443447dbde1f71c24c

Tx prefix hash: be24eadc2e37c5c99413da7eac3c7165a7786b3af057847837b323aba8502327
Tx public key: 519414340657a7d3daa11420fa4c2e7f894d0b2992a2e23da1372e1aa6a073cd
Timestamp: 1727002571 Timestamp [UCT]: 2024-09-22 10:56:11 Age [y:d:h:m:s]: 01:017:01:55:47
Block: 1115614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270557 RingCT/type: yes/0
Extra: 01519414340657a7d3daa11420fa4c2e7f894d0b2992a2e23da1372e1aa6a073cd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c82417eb006ca24ce986cb54e92ae84e9ba598d18040b2720e6178705896a1f2 0.600000000000 1595807 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": 1115624, "vin": [ { "gen": { "height": 1115614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c82417eb006ca24ce986cb54e92ae84e9ba598d18040b2720e6178705896a1f2" } } ], "extra": [ 1, 81, 148, 20, 52, 6, 87, 167, 211, 218, 161, 20, 32, 250, 76, 46, 127, 137, 77, 11, 41, 146, 162, 226, 61, 161, 55, 46, 26, 166, 160, 115, 205, 2, 17, 0, 0, 0, 3, 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