Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0505d75e242080e8707064e6cddccfdc57af5cff289cd0eb2a3cfef47830d8e

Tx prefix hash: bc89db00d21c2290cbedb80bff84f9be1b57c5d89c22d3371be8b47f0b9f402d
Tx public key: c68ee1ce44299d62203d291d957cb34fc95dc755de54f47e33fe6666afc98a45
Timestamp: 1717183856 Timestamp [UCT]: 2024-05-31 19:30:56 Age [y:d:h:m:s]: 00:298:19:24:05
Block: 1034212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213528 RingCT/type: yes/0
Extra: 01c68ee1ce44299d62203d291d957cb34fc95dc755de54f47e33fe6666afc98a4502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee472c7f3592cd9c51681cd60494e5b5d4c7dee509e1e5f8d957fd1bc42066fc 0.600000000000 1502703 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": 1034222, "vin": [ { "gen": { "height": 1034212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee472c7f3592cd9c51681cd60494e5b5d4c7dee509e1e5f8d957fd1bc42066fc" } } ], "extra": [ 1, 198, 142, 225, 206, 68, 41, 157, 98, 32, 61, 41, 29, 149, 124, 179, 79, 201, 93, 199, 85, 222, 84, 244, 126, 51, 254, 102, 102, 175, 201, 138, 69, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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