Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1370afed686a3c19c381a86229d612a714aeb4458af7696ae0cb5c07131038e

Tx prefix hash: b2867a633613d7e227e31cc7e0408b308b8b42e461931a3c72a9b5419501aca1
Tx public key: 3b173b0947ab4fa3f0d7e265e8fcb3178a185fded9b877528a6f8cb7357a5050
Timestamp: 1725243857 Timestamp [UCT]: 2024-09-02 02:24:17 Age [y:d:h:m:s]: 00:227:22:28:11
Block: 1101036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162743 RingCT/type: yes/0
Extra: 013b173b0947ab4fa3f0d7e265e8fcb3178a185fded9b877528a6f8cb7357a5050021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3943f9d10cf4fe10000b30cb4cdaaaabca64e5cd1dda772143e60eec9f272a88 0.600000000000 1577017 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": 1101046, "vin": [ { "gen": { "height": 1101036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3943f9d10cf4fe10000b30cb4cdaaaabca64e5cd1dda772143e60eec9f272a88" } } ], "extra": [ 1, 59, 23, 59, 9, 71, 171, 79, 163, 240, 215, 226, 101, 232, 252, 179, 23, 138, 24, 95, 222, 217, 184, 119, 82, 138, 111, 140, 183, 53, 122, 80, 80, 2, 17, 0, 0, 0, 6, 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