Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3ca4bf76702aa136b4078b96dc60e93b20852e6c106d0f33267982e3a31ff7b

Tx prefix hash: 9f786cfbfd1ed8bcba499ccc5ed3a511478f0959fe081069421293a2e8a15e05
Tx public key: e40e05d3e1fd76b5dfbbe72b873468dcb028265546915c9a3bf8f649bf0e7277
Timestamp: 1710956442 Timestamp [UCT]: 2024-03-20 17:40:42 Age [y:d:h:m:s]: 00:323:10:41:18
Block: 982602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231240 RingCT/type: yes/0
Extra: 01e40e05d3e1fd76b5dfbbe72b873468dcb028265546915c9a3bf8f649bf0e727702110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1c8eca7c6257334026fa5c04ae44791552c390daf404f1b495e507546924921 0.600000000000 1442711 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": 982612, "vin": [ { "gen": { "height": 982602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1c8eca7c6257334026fa5c04ae44791552c390daf404f1b495e507546924921" } } ], "extra": [ 1, 228, 14, 5, 211, 225, 253, 118, 181, 223, 187, 231, 43, 135, 52, 104, 220, 176, 40, 38, 85, 70, 145, 92, 154, 59, 248, 246, 73, 191, 14, 114, 119, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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