Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0f6f92c89ff5e92f6489037560de788d8a5d64adacc7235700bd97ec7acef75

Tx prefix hash: f3aa60ea32fdd0139f0d6e41b5915ea516178bed5721c9bb61f83fc52db6ef73
Tx public key: b2f33ae12b91bdc2e64f135e319ca9315348654fb64b146e41b437c3c3fd8b1e
Timestamp: 1726543591 Timestamp [UCT]: 2024-09-17 03:26:31 Age [y:d:h:m:s]: 01:052:07:56:49
Block: 1111805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295804 RingCT/type: yes/0
Extra: 01b2f33ae12b91bdc2e64f135e319ca9315348654fb64b146e41b437c3c3fd8b1e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76cc1a3c601e207d56fd01374c59b5bae5087a15c04635da721871799ee0b366 0.600000000000 1590894 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": 1111815, "vin": [ { "gen": { "height": 1111805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76cc1a3c601e207d56fd01374c59b5bae5087a15c04635da721871799ee0b366" } } ], "extra": [ 1, 178, 243, 58, 225, 43, 145, 189, 194, 230, 79, 19, 94, 49, 156, 169, 49, 83, 72, 101, 79, 182, 75, 20, 110, 65, 180, 55, 195, 195, 253, 139, 30, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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