Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df86e067a1f868f847a2b813ba13b54496ac02fdcb2bd299636d026bae1e1a0

Tx prefix hash: ef6581f67144b378eada79deed3f9e3cd40b9a5660defe2da3e6417d144cc116
Tx public key: f041dd1b2218cb4b492213e9b0ce3f6d469cc6732c913821a433730fadd18b8d
Timestamp: 1725824558 Timestamp [UCT]: 2024-09-08 19:42:38 Age [y:d:h:m:s]: 00:221:18:45:23
Block: 1105851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158350 RingCT/type: yes/0
Extra: 01f041dd1b2218cb4b492213e9b0ce3f6d469cc6732c913821a433730fadd18b8d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d44ecc06df00da8fbbb94ab68b7ee87ed177bbc8e6ba2354f791564cd963ffa6 0.600000000000 1583332 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": 1105861, "vin": [ { "gen": { "height": 1105851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d44ecc06df00da8fbbb94ab68b7ee87ed177bbc8e6ba2354f791564cd963ffa6" } } ], "extra": [ 1, 240, 65, 221, 27, 34, 24, 203, 75, 73, 34, 19, 233, 176, 206, 63, 109, 70, 156, 198, 115, 44, 145, 56, 33, 164, 51, 115, 15, 173, 209, 139, 141, 2, 17, 0, 0, 0, 3, 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