Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f1bb7b60cc90281068ba9e1bd634cc9c0060e3c79753ce1e66dc4fe64446551

Tx prefix hash: 8344aae3e94c55a5484aed65434e5ba15462de052377d4480b51cc44658d5ca4
Tx public key: d59f4b20c5896bb37c9c352ea83d09cba7525a518e5877b26f8967cce6d822c9
Timestamp: 1738055430 Timestamp [UCT]: 2025-01-28 09:10:30 Age [y:d:h:m:s]: 00:290:04:30:21
Block: 1206843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205136 RingCT/type: yes/0
Extra: 01d59f4b20c5896bb37c9c352ea83d09cba7525a518e5877b26f8967cce6d822c90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 704b3517a10ab3a40f39ec5106c5538eaabe9db246597ff521d3868e24b48e11 0.600000000000 1693556 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": 1206853, "vin": [ { "gen": { "height": 1206843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "704b3517a10ab3a40f39ec5106c5538eaabe9db246597ff521d3868e24b48e11" } } ], "extra": [ 1, 213, 159, 75, 32, 197, 137, 107, 179, 124, 156, 53, 46, 168, 61, 9, 203, 167, 82, 90, 81, 142, 88, 119, 178, 111, 137, 103, 204, 230, 216, 34, 201, 2, 17, 0, 0, 0, 2, 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