Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66073bb68b6e297d839a45e24a121e4f991931bf3edc6c7ff204e706ec9ab1ed

Tx prefix hash: ccff110ebc507308ff8000e979b8cb9ed72a02a41d6c58e1c5a7d9a9a3fb58b2
Tx public key: c61b60fd6047165f095cdfa459b65d3ba767792e0d6df6689a2475728a5aba04
Timestamp: 1722965984 Timestamp [UCT]: 2024-08-06 17:39:44 Age [y:d:h:m:s]: 00:045:18:47:53
Block: 1082141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32806 RingCT/type: yes/0
Extra: 01c61b60fd6047165f095cdfa459b65d3ba767792e0d6df6689a2475728a5aba04021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7e14fb6a6279c5edab3c72b93668746213b5fca666baff35a3d9be50d707fb0 0.600000000000 1555964 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": 1082151, "vin": [ { "gen": { "height": 1082141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7e14fb6a6279c5edab3c72b93668746213b5fca666baff35a3d9be50d707fb0" } } ], "extra": [ 1, 198, 27, 96, 253, 96, 71, 22, 95, 9, 92, 223, 164, 89, 182, 93, 59, 167, 103, 121, 46, 13, 109, 246, 104, 154, 36, 117, 114, 138, 90, 186, 4, 2, 17, 0, 0, 0, 5, 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