Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b014fdfe9a776579eede2ec5882081409bd4ec1961403e0ca274c79e71e1d108

Tx prefix hash: 090d46e5a6b5f566cb51ed5337c5bc43c5c87e9a2eeb2927f50846fd99dd7a50
Tx public key: f55632d9b1a65dff30d4bc62abde7c99b3161196dc2dbc37aedb086f191adbae
Timestamp: 1582085181 Timestamp [UCT]: 2020-02-19 04:06:21 Age [y:d:h:m:s]: 05:279:12:35:17
Block: 67813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1350700 RingCT/type: yes/0
Extra: 01f55632d9b1a65dff30d4bc62abde7c99b3161196dc2dbc37aedb086f191adbae0211000000144943cd9f000000000000000000

1 output(s) for total of 365.877299856000 dcy

stealth address amount amount idx
00: 3622c0627604edf22d1748201bd570c240d9b5870042304af125dd961630222f 365.877299856000 124949 of 0

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": 67823, "vin": [ { "gen": { "height": 67813 } } ], "vout": [ { "amount": 365877299856, "target": { "key": "3622c0627604edf22d1748201bd570c240d9b5870042304af125dd961630222f" } } ], "extra": [ 1, 245, 86, 50, 217, 177, 166, 93, 255, 48, 212, 188, 98, 171, 222, 124, 153, 179, 22, 17, 150, 220, 45, 188, 55, 174, 219, 8, 111, 25, 26, 219, 174, 2, 17, 0, 0, 0, 20, 73, 67, 205, 159, 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