Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0c97e155a4411ad0df8761a59be7c3bfa6cefbffda1d4afe775015e0628ac67

Tx prefix hash: aadfa128675c2a55a13c6611a1b6561290fd3ddd76fdbfe096c36296327f083f
Tx public key: 8376b0e7e9dbc6381a09fa8bc30bc1352a5110ce7f6788fc822eb8ba7ded35a8
Timestamp: 1764561825 Timestamp [UCT]: 2025-12-01 04:03:45 Age [y:d:h:m:s]: 00:057:17:56:04
Block: 1423867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41162 RingCT/type: yes/0
Extra: 018376b0e7e9dbc6381a09fa8bc30bc1352a5110ce7f6788fc822eb8ba7ded35a80211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10b7f2d0af429da51dc1e7e151732882db5d0cc81c00fc1c4f56e02b5165f473 0.600000000000 1912494 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": 1423877, "vin": [ { "gen": { "height": 1423867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10b7f2d0af429da51dc1e7e151732882db5d0cc81c00fc1c4f56e02b5165f473" } } ], "extra": [ 1, 131, 118, 176, 231, 233, 219, 198, 56, 26, 9, 250, 139, 195, 11, 193, 53, 42, 81, 16, 206, 127, 103, 136, 252, 130, 46, 184, 186, 125, 237, 53, 168, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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