Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8388b339a2efc6ea8dea254469f721e39699e07f18ce840b652edab3bc6449b

Tx prefix hash: 1958a953b9392fc65b09f0b967cf06035bc5f9ebfa542c0808aa2d73b40b8895
Tx public key: 8b2c49f06a2f8178e31111b6952af6eca846a31de639d11d0b4a05771d30f944
Timestamp: 1754693221 Timestamp [UCT]: 2025-08-08 22:47:01 Age [y:d:h:m:s]: 00:014:20:44:25
Block: 1343106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9795 RingCT/type: yes/0
Extra: 018b2c49f06a2f8178e31111b6952af6eca846a31de639d11d0b4a05771d30f9440211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c15f9b1a9810ca8f5eae67f0b005be7e2cd46f5bc3b12da3fd9db234f5969e0 0.600000000000 1830941 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": 1343116, "vin": [ { "gen": { "height": 1343106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c15f9b1a9810ca8f5eae67f0b005be7e2cd46f5bc3b12da3fd9db234f5969e0" } } ], "extra": [ 1, 139, 44, 73, 240, 106, 47, 129, 120, 227, 17, 17, 182, 149, 42, 246, 236, 168, 70, 163, 29, 230, 57, 209, 29, 11, 74, 5, 119, 29, 48, 249, 68, 2, 17, 0, 0, 0, 3, 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