Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc1f97a3d9e2dbb777d3bb69a5bf132b430161ae85962321a1030538282b4435

Tx prefix hash: b039cd3ae6ba35f0e45bb706c42cc7576a9ca21797f6ba242ac256b02729200e
Tx public key: 740024e50a712270f5b14b20a90f435bed9bd65f7c85141f5ad2f5a85d41ba0f
Timestamp: 1721016139 Timestamp [UCT]: 2024-07-15 04:02:19 Age [y:d:h:m:s]: 00:268:00:15:42
Block: 1065990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191461 RingCT/type: yes/0
Extra: 01740024e50a712270f5b14b20a90f435bed9bd65f7c85141f5ad2f5a85d41ba0f02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3618f8a4e449466ae0e2c6e306c47b9d6d930bb41279eaac0b6126a09e44ed81 0.600000000000 1536561 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": 1066000, "vin": [ { "gen": { "height": 1065990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3618f8a4e449466ae0e2c6e306c47b9d6d930bb41279eaac0b6126a09e44ed81" } } ], "extra": [ 1, 116, 0, 36, 229, 10, 113, 34, 112, 245, 177, 75, 32, 169, 15, 67, 91, 237, 155, 214, 95, 124, 133, 20, 31, 90, 210, 245, 168, 93, 65, 186, 15, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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