Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3668844ae22232b382c64dfc6bcbb52713379363133e436430cf9c6960fa1cd5

Tx prefix hash: a012ed6a71d4d6993d31df603f8d8e3f734cc39b7bd1722cc952ee8372769b50
Tx public key: 4f4844d06f28b5cc220853bf6fa8d1b973a135414e5df531ccd5a3437bc82796
Timestamp: 1757364950 Timestamp [UCT]: 2025-09-08 20:55:50 Age [y:d:h:m:s]: 00:146:07:49:14
Block: 1364310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104499 RingCT/type: yes/0
Extra: 014f4844d06f28b5cc220853bf6fa8d1b973a135414e5df531ccd5a3437bc8279602110000000bad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6c50290ddd108c0f5cb823680398fd256379fd5e9458f146b13b6d4d5d4eaf5 0.600000000000 1852349 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": 1364320, "vin": [ { "gen": { "height": 1364310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6c50290ddd108c0f5cb823680398fd256379fd5e9458f146b13b6d4d5d4eaf5" } } ], "extra": [ 1, 79, 72, 68, 208, 111, 40, 181, 204, 34, 8, 83, 191, 111, 168, 209, 185, 115, 161, 53, 65, 78, 93, 245, 49, 204, 213, 163, 67, 123, 200, 39, 150, 2, 17, 0, 0, 0, 11, 173, 121, 72, 208, 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