Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf55eca47088aca8e0486f46cab998e3ea66849596a542d068d22241278e7a6

Tx prefix hash: 79963b505694b4cf37165d8ab36bff1f257fb559b7a6c09b21e60f5ff929f10d
Tx public key: f8d6158ef9789d249364eec2491b3f608f8cf7fac513ec25f5f9693b50e033a4
Timestamp: 1699647537 Timestamp [UCT]: 2023-11-10 20:18:57 Age [y:d:h:m:s]: 01:082:09:49:07
Block: 888831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320058 RingCT/type: yes/0
Extra: 01f8d6158ef9789d249364eec2491b3f608f8cf7fac513ec25f5f9693b50e033a402110000000833af99f4000000000000000000

1 output(s) for total of 0.696520536000 dcy

stealth address amount amount idx
00: bc3d986eb1112c10634612e1ab483d472ea13afd0ab97424c5b797800847489d 0.696520536000 1344790 of 0

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": 888841, "vin": [ { "gen": { "height": 888831 } } ], "vout": [ { "amount": 696520536, "target": { "key": "bc3d986eb1112c10634612e1ab483d472ea13afd0ab97424c5b797800847489d" } } ], "extra": [ 1, 248, 214, 21, 142, 249, 120, 157, 36, 147, 100, 238, 194, 73, 27, 63, 96, 143, 140, 247, 250, 197, 19, 236, 37, 245, 249, 105, 59, 80, 224, 51, 164, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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