Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c475039f99f29795492d90fa0bc33a2d490d20b2b2ead9fd6938c811547d148

Tx prefix hash: ed88fc65604c098c34ded384d4ff7ef995456d65f8837e82cf23bf41fcad5443
Tx public key: 35ce8bd7b3ea4177fce39ced3f3b8f70cf7e46d025e8ea3d6bc41d10b3568f35
Timestamp: 1740643143 Timestamp [UCT]: 2025-02-27 07:59:03 Age [y:d:h:m:s]: 00:266:15:23:09
Block: 1228225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188331 RingCT/type: yes/0
Extra: 0135ce8bd7b3ea4177fce39ced3f3b8f70cf7e46d025e8ea3d6bc41d10b3568f3502110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 576fe1658d3fcecfbdb527e7bd34c03b5a38b6efdadb5fdab395501da6ea19ae 0.600000000000 1715102 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": 1228235, "vin": [ { "gen": { "height": 1228225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "576fe1658d3fcecfbdb527e7bd34c03b5a38b6efdadb5fdab395501da6ea19ae" } } ], "extra": [ 1, 53, 206, 139, 215, 179, 234, 65, 119, 252, 227, 156, 237, 63, 59, 143, 112, 207, 126, 70, 208, 37, 232, 234, 61, 107, 196, 29, 16, 179, 86, 143, 53, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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