Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81392303e9eeb97df1de9943cfe65da202ae30460c0ca944f10aab0b64d33f64

Tx prefix hash: e7b8b570ee69f0f2cb3c194be31fb6ea9df2db659d981ef822fe67b0ee6bf892
Tx public key: d1cd7328d8beb68d870b15d1b39f7330311690d7f8fb116bd81398376a70ade1
Timestamp: 1717915197 Timestamp [UCT]: 2024-06-09 06:39:57 Age [y:d:h:m:s]: 00:293:03:28:44
Block: 1040269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209494 RingCT/type: yes/0
Extra: 01d1cd7328d8beb68d870b15d1b39f7330311690d7f8fb116bd81398376a70ade10211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9e12d58095d489661c8209e9fd64734437d1e43add4b760b6c4f9737291b405 0.600000000000 1508926 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": 1040279, "vin": [ { "gen": { "height": 1040269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9e12d58095d489661c8209e9fd64734437d1e43add4b760b6c4f9737291b405" } } ], "extra": [ 1, 209, 205, 115, 40, 216, 190, 182, 141, 135, 11, 21, 209, 179, 159, 115, 48, 49, 22, 144, 215, 248, 251, 17, 107, 216, 19, 152, 55, 106, 112, 173, 225, 2, 17, 0, 0, 0, 6, 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