Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a50a4516c16d154c629dc40304f03b8443168d7066d60961592c830b68d5a378

Tx prefix hash: d3492cd152fc7ff52ba6ca859962bfb2b4b09619bc6d8831f2b37e4475f46a9c
Tx public key: cf6cbbc880f6d468129d3ec90a728527ba6bda06e9af4cac958ce082d777a3a5
Timestamp: 1751643327 Timestamp [UCT]: 2025-07-04 15:35:27 Age [y:d:h:m:s]: 00:132:21:59:45
Block: 1318696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93281 RingCT/type: yes/0
Extra: 01cf6cbbc880f6d468129d3ec90a728527ba6bda06e9af4cac958ce082d777a3a5021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1393de3a076fb27f6baac8e6d14d7681e12c45b5e549ea04ad8161ce2b3d61c 0.600000000000 1806381 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": 1318706, "vin": [ { "gen": { "height": 1318696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1393de3a076fb27f6baac8e6d14d7681e12c45b5e549ea04ad8161ce2b3d61c" } } ], "extra": [ 1, 207, 108, 187, 200, 128, 246, 212, 104, 18, 157, 62, 201, 10, 114, 133, 39, 186, 107, 218, 6, 233, 175, 76, 172, 149, 140, 224, 130, 215, 119, 163, 165, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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