Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93a0d735fbd389b209aa4b06f5f5e1c03f762dd8064d661c2fcbd8e907fab847

Tx prefix hash: f8534adcdd1f987f8c40f95b1d75bcfc1519d977319c2cb4e64307eb287e3ab7
Tx public key: 019bb3fe99748eef17247d0e41d402a3c9522c27077cd9b756c11f048021de89
Timestamp: 1707886799 Timestamp [UCT]: 2024-02-14 04:59:59 Age [y:d:h:m:s]: 01:053:19:42:32
Block: 957120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299496 RingCT/type: yes/0
Extra: 01019bb3fe99748eef17247d0e41d402a3c9522c27077cd9b756c11f048021de8902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b11e8580ecdf37c4e1e098a06677868c0034e267717c1b394ab3fe6774eb5e2 0.600000000000 1416436 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": 957130, "vin": [ { "gen": { "height": 957120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b11e8580ecdf37c4e1e098a06677868c0034e267717c1b394ab3fe6774eb5e2" } } ], "extra": [ 1, 1, 155, 179, 254, 153, 116, 142, 239, 23, 36, 125, 14, 65, 212, 2, 163, 201, 82, 44, 39, 7, 124, 217, 183, 86, 193, 31, 4, 128, 33, 222, 137, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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