Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 118bb39cb9450e49895b322f0e54e8bcfb51878f47f3f2ddd3c6329db84134b6

Tx prefix hash: d746edf00c150575d55e2c74578f19f7e5137d020622f7a167dbdb1e50103f5c
Tx public key: 3398e64028a335270e63b9f3565ab7242a9f4c8dd93dfd738931204db5287b5c
Timestamp: 1717889615 Timestamp [UCT]: 2024-06-08 23:33:35 Age [y:d:h:m:s]: 01:152:03:37:26
Block: 1040061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367312 RingCT/type: yes/0
Extra: 013398e64028a335270e63b9f3565ab7242a9f4c8dd93dfd738931204db5287b5c0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dc817d00c164f27c61322c864c556ae83cacc03935d672cb547d05d7e381f7e 0.600000000000 1508716 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": 1040071, "vin": [ { "gen": { "height": 1040061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dc817d00c164f27c61322c864c556ae83cacc03935d672cb547d05d7e381f7e" } } ], "extra": [ 1, 51, 152, 230, 64, 40, 163, 53, 39, 14, 99, 185, 243, 86, 90, 183, 36, 42, 159, 76, 141, 217, 61, 253, 115, 137, 49, 32, 77, 181, 40, 123, 92, 2, 17, 0, 0, 0, 7, 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