Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b48f3cb6ec6b28317094e87fba5a638b85aa75dd45d9922fcc99cec1f14c790

Tx prefix hash: e88ec5c2e89a569067344bddd15e7bc4be2440d4c8ba448a8e3696fb24f8a0dc
Tx public key: 3d233c4d12a38cedaa364e522803b7bb323cb4c8ecb343e54eab8fd2c102c046
Timestamp: 1734944158 Timestamp [UCT]: 2024-12-23 08:55:58 Age [y:d:h:m:s]: 00:095:10:17:38
Block: 1181359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67963 RingCT/type: yes/0
Extra: 013d233c4d12a38cedaa364e522803b7bb323cb4c8ecb343e54eab8fd2c102c0460211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 989cd136c8a5ea498874d603f14cbca0c5b4ff325b9440670661b82d8d736598 0.600000000000 1667778 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": 1181369, "vin": [ { "gen": { "height": 1181359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "989cd136c8a5ea498874d603f14cbca0c5b4ff325b9440670661b82d8d736598" } } ], "extra": [ 1, 61, 35, 60, 77, 18, 163, 140, 237, 170, 54, 78, 82, 40, 3, 183, 187, 50, 60, 180, 200, 236, 179, 67, 229, 78, 171, 143, 210, 193, 2, 192, 70, 2, 17, 0, 0, 0, 7, 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