Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e178a6f7c73cbcee1a071466478930eebe4e2fdd2173f0d03017589a4d8256cf

Tx prefix hash: 6895b2c14509d20bb09bce2867e252b25ebf3117a8eca2892b29f54a828bfb20
Tx public key: 85b56a03385381fdf8fe0759a2d74a36f04cbec3bb35801a0bce4b2315a4c10f
Timestamp: 1739435623 Timestamp [UCT]: 2025-02-13 08:33:43 Age [y:d:h:m:s]: 00:236:23:16:19
Block: 1218253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167051 RingCT/type: yes/0
Extra: 0185b56a03385381fdf8fe0759a2d74a36f04cbec3bb35801a0bce4b2315a4c10f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e9c94c0ea90a668d5c7a327a87ffc056d602721dc5dc4aa96ff96a068370568 0.600000000000 1705068 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": 1218263, "vin": [ { "gen": { "height": 1218253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e9c94c0ea90a668d5c7a327a87ffc056d602721dc5dc4aa96ff96a068370568" } } ], "extra": [ 1, 133, 181, 106, 3, 56, 83, 129, 253, 248, 254, 7, 89, 162, 215, 74, 54, 240, 76, 190, 195, 187, 53, 128, 26, 11, 206, 75, 35, 21, 164, 193, 15, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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