Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8423e6a1d25e05274125c03b46b86f6af6adf2b54ce400924098af839a2b667e

Tx prefix hash: 85f2f3d08e49a0b9b1dc28467391824260eba8c5437df6002c723b97720e8bbc
Tx public key: 905cf859bcb112026c47fbfa5ff6f88e65913083c00c37dbd643c5659007dd89
Timestamp: 1733925964 Timestamp [UCT]: 2024-12-11 14:06:04 Age [y:d:h:m:s]: 00:331:09:57:01
Block: 1172909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234369 RingCT/type: yes/0
Extra: 01905cf859bcb112026c47fbfa5ff6f88e65913083c00c37dbd643c5659007dd890211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cbfe99a0c2596ad1cdf8a18d1a9eac0a8f81a5a3a3865c6ebc17800372a54d0 0.600000000000 1658868 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": 1172919, "vin": [ { "gen": { "height": 1172909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cbfe99a0c2596ad1cdf8a18d1a9eac0a8f81a5a3a3865c6ebc17800372a54d0" } } ], "extra": [ 1, 144, 92, 248, 89, 188, 177, 18, 2, 108, 71, 251, 250, 95, 246, 248, 142, 101, 145, 48, 131, 192, 12, 55, 219, 214, 67, 197, 101, 144, 7, 221, 137, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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