Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 958792375c8d75dce9a3b14929fc93bf570013840f49417b0d62bd08cfc32dd3

Tx prefix hash: e355103d1aa1965fd77705e995632c8f08f8422a0a921e6e4b69fe9d76b313a8
Tx public key: 1c1e6e71ac3f8d8556bebde54424fd436e7d1bb479ea8bc3848c2d0f9b199d7d
Timestamp: 1731954024 Timestamp [UCT]: 2024-11-18 18:20:24 Age [y:d:h:m:s]: 01:002:13:24:26
Block: 1156552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260247 RingCT/type: yes/0
Extra: 011c1e6e71ac3f8d8556bebde54424fd436e7d1bb479ea8bc3848c2d0f9b199d7d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d5c514d4892a336460fa2f3d26f75f5a0e44aa72d4b843c5585274f495759f0 0.600000000000 1642175 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": 1156562, "vin": [ { "gen": { "height": 1156552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d5c514d4892a336460fa2f3d26f75f5a0e44aa72d4b843c5585274f495759f0" } } ], "extra": [ 1, 28, 30, 110, 113, 172, 63, 141, 133, 86, 190, 189, 229, 68, 36, 253, 67, 110, 125, 27, 180, 121, 234, 139, 195, 132, 140, 45, 15, 155, 25, 157, 125, 2, 17, 0, 0, 0, 1, 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