Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c63fc8cdae8073418cf666547910c1d92dbc24cd843a0d107e6e9348f0bd92f

Tx prefix hash: 695d689b925fb1bd98963307b138b003e5109de584e36bd7616cff0e6427aa8f
Tx public key: 9256501742d2f642595e0c4b3e05c7b543f933f51d4297f112e509b60a7229a7
Timestamp: 1743200245 Timestamp [UCT]: 2025-03-28 22:17:25 Age [y:d:h:m:s]: 00:284:13:51:32
Block: 1249406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201200 RingCT/type: yes/0
Extra: 019256501742d2f642595e0c4b3e05c7b543f933f51d4297f112e509b60a7229a70211000000029ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4c942e73b4ce28de318c455aa810d1177b763353438024f2fef14fa08aacd36 0.600000000000 1736445 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": 1249416, "vin": [ { "gen": { "height": 1249406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4c942e73b4ce28de318c455aa810d1177b763353438024f2fef14fa08aacd36" } } ], "extra": [ 1, 146, 86, 80, 23, 66, 210, 246, 66, 89, 94, 12, 75, 62, 5, 199, 181, 67, 249, 51, 245, 29, 66, 151, 241, 18, 229, 9, 182, 10, 114, 41, 167, 2, 17, 0, 0, 0, 2, 155, 166, 41, 223, 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