Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04020a10950bc4bb77ede1f04451275905865b1ac6d232e6b10c9d569cb1d9a8

Tx prefix hash: 8a959d7cac46b98db836bdbe88694b971f6202a290d0c241bca444381a2242cf
Tx public key: 1ea165a2934a7ba2d29cfa14e4b2c66701d5d4af59521ac50880dacde05f9bc8
Timestamp: 1745101739 Timestamp [UCT]: 2025-04-19 22:28:59 Age [y:d:h:m:s]: 00:287:22:52:22
Block: 1265154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203439 RingCT/type: yes/0
Extra: 011ea165a2934a7ba2d29cfa14e4b2c66701d5d4af59521ac50880dacde05f9bc8021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68e7e11ca338d123611b9898fd761b3e1aa51951c6a99dc09dc16c91b1e299d2 0.600000000000 1752357 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": 1265164, "vin": [ { "gen": { "height": 1265154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68e7e11ca338d123611b9898fd761b3e1aa51951c6a99dc09dc16c91b1e299d2" } } ], "extra": [ 1, 30, 161, 101, 162, 147, 74, 123, 162, 210, 156, 250, 20, 228, 178, 198, 103, 1, 213, 212, 175, 89, 82, 26, 197, 8, 128, 218, 205, 224, 95, 155, 200, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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