Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ea60f5979a39d1293d8fc1e3a0db203e80a8c7e8c5add177b55d8746a3e9be6

Tx prefix hash: f3558e00afd2e1c147a962dbd68346ff17556807b450105233425951429430ab
Tx public key: eebbf555d17ba406ef883c7d4abd8e5820f2a83c81a247a75b1c25a8c97832d1
Timestamp: 1722370159 Timestamp [UCT]: 2024-07-30 20:09:19 Age [y:d:h:m:s]: 00:259:10:55:22
Block: 1077196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185350 RingCT/type: yes/0
Extra: 01eebbf555d17ba406ef883c7d4abd8e5820f2a83c81a247a75b1c25a8c97832d102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f6116ba4c895a0a4bef497a7e3a12466e1617bbc2959ac6ef796aae31087750 0.600000000000 1549743 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": 1077206, "vin": [ { "gen": { "height": 1077196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f6116ba4c895a0a4bef497a7e3a12466e1617bbc2959ac6ef796aae31087750" } } ], "extra": [ 1, 238, 187, 245, 85, 209, 123, 164, 6, 239, 136, 60, 125, 74, 189, 142, 88, 32, 242, 168, 60, 129, 162, 71, 167, 91, 28, 37, 168, 201, 120, 50, 209, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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