Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e445afc51a75da7e7723c7895be8353cb685f0e2cf026dfa24a7f8f618b3dcb

Tx prefix hash: 55ccf6710ba2e44f286da3d5b178918565e32f8f29ac36ac20232a27f093ebce
Tx public key: cd20f4035e9dea325b6eec37e8a4f76bd0eeb45d2e0e26068bf85beb862e307b
Timestamp: 1696070528 Timestamp [UCT]: 2023-09-30 10:42:08 Age [y:d:h:m:s]: 01:108:15:30:40
Block: 859377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338913 RingCT/type: yes/0
Extra: 01cd20f4035e9dea325b6eec37e8a4f76bd0eeb45d2e0e26068bf85beb862e307b02110000000d4b8f5122000000000000000000

1 output(s) for total of 0.872021710000 dcy

stealth address amount amount idx
00: d1867fbc3bd4eb74495bb5a31047cccba0cf4b6429a1c89ffccb33d41ccf9892 0.872021710000 1313601 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": 859387, "vin": [ { "gen": { "height": 859377 } } ], "vout": [ { "amount": 872021710, "target": { "key": "d1867fbc3bd4eb74495bb5a31047cccba0cf4b6429a1c89ffccb33d41ccf9892" } } ], "extra": [ 1, 205, 32, 244, 3, 94, 157, 234, 50, 91, 110, 236, 55, 232, 164, 247, 107, 208, 238, 180, 93, 46, 14, 38, 6, 139, 248, 91, 235, 134, 46, 48, 123, 2, 17, 0, 0, 0, 13, 75, 143, 81, 34, 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