Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966fca2eea0129c2c2d7d7916a11ed9de65db9075374e496f722ebc70772cb04

Tx prefix hash: 536e818302150efea514b22362d341232e4a25a1f74a77d09ff451385ead68f7
Tx public key: 751f248b3754a3cad139e545c73cb02415a67ba6490f9bfd8158c7797df9da8a
Timestamp: 1708233351 Timestamp [UCT]: 2024-02-18 05:15:51 Age [y:d:h:m:s]: 01:046:11:58:33
Block: 960003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294261 RingCT/type: yes/0
Extra: 01751f248b3754a3cad139e545c73cb02415a67ba6490f9bfd8158c7797df9da8a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f4380dbd94ac4c24361257a31661654b8da48689a8fc6d3732563f730b748e7 0.600000000000 1419562 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": 960013, "vin": [ { "gen": { "height": 960003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f4380dbd94ac4c24361257a31661654b8da48689a8fc6d3732563f730b748e7" } } ], "extra": [ 1, 117, 31, 36, 139, 55, 84, 163, 202, 209, 57, 229, 69, 199, 60, 176, 36, 21, 166, 123, 166, 73, 15, 155, 253, 129, 88, 199, 121, 125, 249, 218, 138, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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