Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7074c1aa4c546a700fd17aa13869bfab8a46815cbe41029515c2954c07b1ea3

Tx prefix hash: 689ff13381c9f8298a62500c0b5076be70a7ddd003b8815bfc0bdd2161eaa793
Tx public key: f7cdc800a8f7a5203c8426093e6cd155557d8af2bd4967bbd7ada5f82fb5d507
Timestamp: 1760128376 Timestamp [UCT]: 2025-10-10 20:32:56 Age [y:d:h:m:s]: 00:055:20:20:51
Block: 1387126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39975 RingCT/type: yes/0
Extra: 01f7cdc800a8f7a5203c8426093e6cd155557d8af2bd4967bbd7ada5f82fb5d507021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65e9c01a016bceb9cc3631a4e5c9e6febd1808f85571980d8f84464e4c3daf7f 0.600000000000 1875313 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": 1387136, "vin": [ { "gen": { "height": 1387126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65e9c01a016bceb9cc3631a4e5c9e6febd1808f85571980d8f84464e4c3daf7f" } } ], "extra": [ 1, 247, 205, 200, 0, 168, 247, 165, 32, 60, 132, 38, 9, 62, 108, 209, 85, 85, 125, 138, 242, 189, 73, 103, 187, 215, 173, 165, 248, 47, 181, 213, 7, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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