Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cac642bb545c8d9d8f4efc7a13dbfffe898d0ede282b2923e60b4257ee5a4628

Tx prefix hash: b8bea6e3cc49aed68f58c91e05729c53b40dc40eed45068e40dd42412f536c6e
Tx public key: 855a98fd62d6b76850e17184bdca59dcea2910f7f6058b17bd97ddd1d69b5f8f
Timestamp: 1762384247 Timestamp [UCT]: 2025-11-05 23:10:47 Age [y:d:h:m:s]: 00:052:01:07:48
Block: 1405801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37286 RingCT/type: yes/0
Extra: 01855a98fd62d6b76850e17184bdca59dcea2910f7f6058b17bd97ddd1d69b5f8f0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 969ae418110eb22ca1f652de0e6f6fdd0aa215e4c642112405712d658e7c74f8 0.600000000000 1894182 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": 1405811, "vin": [ { "gen": { "height": 1405801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "969ae418110eb22ca1f652de0e6f6fdd0aa215e4c642112405712d658e7c74f8" } } ], "extra": [ 1, 133, 90, 152, 253, 98, 214, 183, 104, 80, 225, 113, 132, 189, 202, 89, 220, 234, 41, 16, 247, 246, 5, 139, 23, 189, 151, 221, 209, 214, 155, 95, 143, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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