Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6593e644111940824f91a701b394f5d2ff0bd0d2c6e3a8cce1d2b97577e0b59d

Tx prefix hash: 17bd0fe92809421eacd2675ac05896bce59a139a3f93c0f965fe1b0464b5e8c7
Tx public key: 0b6e3177df0db415dcbfa742c4d1c8b1b4441e739fec0bee77c48ec7527e8c48
Timestamp: 1697162167 Timestamp [UCT]: 2023-10-13 01:56:07 Age [y:d:h:m:s]: 01:250:08:01:37
Block: 868416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439859 RingCT/type: yes/0
Extra: 010b6e3177df0db415dcbfa742c4d1c8b1b4441e739fec0bee77c48ec7527e8c4802110000000575e3f0e9000000000000000000

1 output(s) for total of 0.813911763000 dcy

stealth address amount amount idx
00: ae790a1ce27482dd318e9bcd18e518d4eb237c2012b38118675750172a3d969a 0.813911763000 1323223 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": 868426, "vin": [ { "gen": { "height": 868416 } } ], "vout": [ { "amount": 813911763, "target": { "key": "ae790a1ce27482dd318e9bcd18e518d4eb237c2012b38118675750172a3d969a" } } ], "extra": [ 1, 11, 110, 49, 119, 223, 13, 180, 21, 220, 191, 167, 66, 196, 209, 200, 177, 180, 68, 30, 115, 159, 236, 11, 238, 119, 196, 142, 199, 82, 126, 140, 72, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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