Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c756f06c9b90332f5c7d58d608a8d241a9dc773c4afe57daa531a63a25df210b

Tx prefix hash: 3dd92e8aa1b1c50100ae1dba552cbb63c890c1f6f359f031fc4509d53cb058ad
Tx public key: f6b9cc65d431504fbe7f90f834a7935ad9df756cdede21e95823af51fb9b6183
Timestamp: 1721530876 Timestamp [UCT]: 2024-07-21 03:01:16 Age [y:d:h:m:s]: 00:262:15:32:20
Block: 1070241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187637 RingCT/type: yes/0
Extra: 01f6b9cc65d431504fbe7f90f834a7935ad9df756cdede21e95823af51fb9b61830211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95ecbe2c7840d2a8f1c2015bba37045028fcd91f903be1d6e95a371a0eab3959 0.600000000000 1541994 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": 1070251, "vin": [ { "gen": { "height": 1070241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95ecbe2c7840d2a8f1c2015bba37045028fcd91f903be1d6e95a371a0eab3959" } } ], "extra": [ 1, 246, 185, 204, 101, 212, 49, 80, 79, 190, 127, 144, 248, 52, 167, 147, 90, 217, 223, 117, 108, 222, 222, 33, 233, 88, 35, 175, 81, 251, 155, 97, 131, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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