Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3a55bf9713e5865c9583774239051409c9ea9b204b3526156d6bbd102700df5

Tx prefix hash: 66e19346b23a839b940f5b48fac7425c7af5da8ec12bf9d19e93a9a024e0f8c4
Tx public key: cb5f30633fc21efc1bf7d51653d5184c7913b1009b4c2fdc92689410f0ad9d80
Timestamp: 1681408542 Timestamp [UCT]: 2023-04-13 17:55:42 Age [y:d:h:m:s]: 01:272:21:16:07
Block: 737849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456538 RingCT/type: yes/0
Extra: 01cb5f30633fc21efc1bf7d51653d5184c7913b1009b4c2fdc92689410f0ad9d80021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.203942137000 dcy

stealth address amount amount idx
00: 1fdeaf582f5dbaa9ba645a527f238213175d00cd9f8811e44ce50dc7e0c7d6b5 2.203942137000 1184460 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": 737859, "vin": [ { "gen": { "height": 737849 } } ], "vout": [ { "amount": 2203942137, "target": { "key": "1fdeaf582f5dbaa9ba645a527f238213175d00cd9f8811e44ce50dc7e0c7d6b5" } } ], "extra": [ 1, 203, 95, 48, 99, 63, 194, 30, 252, 27, 247, 213, 22, 83, 213, 24, 76, 121, 19, 177, 0, 155, 76, 47, 220, 146, 104, 148, 16, 240, 173, 157, 128, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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