Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3815f829f5b89e53707cbd40f3b0d643b421b010b6a812df5f57600421d4b807

Tx prefix hash: 4ce35fec7213dfebf94a509a6f77a2d5fab8330053af7dfcb841e14cff2336b8
Tx public key: 8ade027228b8dcfc075c2595c7a07232666ff89401272a85b4550b7a51127dcb
Timestamp: 1732897123 Timestamp [UCT]: 2024-11-29 16:18:43 Age [y:d:h:m:s]: 00:129:17:49:26
Block: 1164383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92521 RingCT/type: yes/0
Extra: 018ade027228b8dcfc075c2595c7a07232666ff89401272a85b4550b7a51127dcb0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 446e5c5cea48bdd8a6d856fe3388b0d38d3126a358af29cbcf1fffea3de17057 0.600000000000 1650056 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": 1164393, "vin": [ { "gen": { "height": 1164383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "446e5c5cea48bdd8a6d856fe3388b0d38d3126a358af29cbcf1fffea3de17057" } } ], "extra": [ 1, 138, 222, 2, 114, 40, 184, 220, 252, 7, 92, 37, 149, 199, 160, 114, 50, 102, 111, 248, 148, 1, 39, 42, 133, 180, 85, 11, 122, 81, 18, 125, 203, 2, 17, 0, 0, 0, 6, 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