Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291e5dc6d96f452c9a0f25e154c2836575d0bde721f44c3cedb7990e3d0035ed

Tx prefix hash: 202c29e186430ce03724ff9d290fe96ef59b4594bfdbf672f433ae1f4dd5f792
Tx public key: 33b68f517947fc7c961a6a27bba8275e058ba4d907dddac6a60f4efd083b74d0
Timestamp: 1718551646 Timestamp [UCT]: 2024-06-16 15:27:26 Age [y:d:h:m:s]: 00:220:22:00:19
Block: 1045564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158032 RingCT/type: yes/0
Extra: 0133b68f517947fc7c961a6a27bba8275e058ba4d907dddac6a60f4efd083b74d002110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d48fbc997097c9c3b5b35a6c84439c8ba0982ab25cbec35287bbe1450fcb1665 0.600000000000 1515167 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": 1045574, "vin": [ { "gen": { "height": 1045564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d48fbc997097c9c3b5b35a6c84439c8ba0982ab25cbec35287bbe1450fcb1665" } } ], "extra": [ 1, 51, 182, 143, 81, 121, 71, 252, 124, 150, 26, 106, 39, 187, 168, 39, 94, 5, 139, 164, 217, 7, 221, 218, 198, 166, 15, 78, 253, 8, 59, 116, 208, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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