Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c6e60ff31959a465281aefa22d57db8812128f7ef0355a6fcf2e40d037dcb37

Tx prefix hash: 9bf0ce92d24893496a477bd315a4d11fc2883a6a8ee87572a2b5e5c5ec679b86
Tx public key: ccfea9539fe6f220d842d77fe7a3ec9f69237e212e5c9908ad2ab0b9c9749122
Timestamp: 1718516606 Timestamp [UCT]: 2024-06-16 05:43:26 Age [y:d:h:m:s]: 01:143:05:00:20
Block: 1045276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360867 RingCT/type: yes/0
Extra: 01ccfea9539fe6f220d842d77fe7a3ec9f69237e212e5c9908ad2ab0b9c97491220211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bbf14180eebf55a4a7d67324947499b757f57d52246493f2ea1c1c70ca30129 0.600000000000 1514801 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": 1045286, "vin": [ { "gen": { "height": 1045276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bbf14180eebf55a4a7d67324947499b757f57d52246493f2ea1c1c70ca30129" } } ], "extra": [ 1, 204, 254, 169, 83, 159, 230, 242, 32, 216, 66, 215, 127, 231, 163, 236, 159, 105, 35, 126, 33, 46, 92, 153, 8, 173, 42, 176, 185, 201, 116, 145, 34, 2, 17, 0, 0, 0, 1, 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