Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18704f14f8e53eb714b1ec1615dfb7ca224da5446177080d523f3add5cec3a08

Tx prefix hash: 005adde666d799ee06318453ca913c720d100a48386f7d3ac33f8d19292ee0e1
Tx public key: a84e01ed603a830fe39510e12a101989ce47b380d1ee02e42d2f6c2c1d0b87b2
Timestamp: 1713762330 Timestamp [UCT]: 2024-04-22 05:05:30 Age [y:d:h:m:s]: 00:346:21:05:02
Block: 1005839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247969 RingCT/type: yes/0
Extra: 01a84e01ed603a830fe39510e12a101989ce47b380d1ee02e42d2f6c2c1d0b87b20211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e4fac46caa40c77462c9656f48cdba163d8ee46a3a208a5d05217d5dea3bc5e 0.600000000000 1466657 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": 1005849, "vin": [ { "gen": { "height": 1005839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e4fac46caa40c77462c9656f48cdba163d8ee46a3a208a5d05217d5dea3bc5e" } } ], "extra": [ 1, 168, 78, 1, 237, 96, 58, 131, 15, 227, 149, 16, 225, 42, 16, 25, 137, 206, 71, 179, 128, 209, 238, 2, 228, 45, 47, 108, 44, 29, 11, 135, 178, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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