Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a1e884a487fb5f15576017c72730d8f5cc566611b20192988d2809f1ec41ceb

Tx prefix hash: 4a11a382b1435e6024dfe18e90b15f6c2d4ce37c785fc3e26b2a9bb6510068dd
Tx public key: 457a2bb494630fe3801fb9feb8b0051d1ff473ec0e318844b8001ff234ce4d33
Timestamp: 1713843712 Timestamp [UCT]: 2024-04-23 03:41:52 Age [y:d:h:m:s]: 00:253:09:47:37
Block: 1006517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181389 RingCT/type: yes/0
Extra: 01457a2bb494630fe3801fb9feb8b0051d1ff473ec0e318844b8001ff234ce4d330211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 317c53cc4c4b75d65ccc528b742d58059719b89cd7a37e483cd2e3cbd2e28b2d 0.600000000000 1467571 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": 1006527, "vin": [ { "gen": { "height": 1006517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "317c53cc4c4b75d65ccc528b742d58059719b89cd7a37e483cd2e3cbd2e28b2d" } } ], "extra": [ 1, 69, 122, 43, 180, 148, 99, 15, 227, 128, 31, 185, 254, 184, 176, 5, 29, 31, 244, 115, 236, 14, 49, 136, 68, 184, 0, 31, 242, 52, 206, 77, 51, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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