Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d577736fec8fe4924423f448009246e06c87f593cf220b2e29ad926936f2108

Tx prefix hash: 8d2eb206f5ed8e297bcb06995aea3c0d10fd1d8f72f7e291befeb3d622156552
Tx public key: 6097c0f7757ec7ae63a6171c423da7b5d4263645b4aa908c44d7a8df2dc12309
Timestamp: 1699689060 Timestamp [UCT]: 2023-11-11 07:51:00 Age [y:d:h:m:s]: 01:159:07:02:17
Block: 889174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375041 RingCT/type: yes/0
Extra: 016097c0f7757ec7ae63a6171c423da7b5d4263645b4aa908c44d7a8df2dc1230902110000000775e3f0e9000000000000000000

1 output(s) for total of 0.694700199000 dcy

stealth address amount amount idx
00: 614796a535c2f4756065b332a251fb0056410fd462a5b8f3244f950e62b5fb2b 0.694700199000 1345151 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": 889184, "vin": [ { "gen": { "height": 889174 } } ], "vout": [ { "amount": 694700199, "target": { "key": "614796a535c2f4756065b332a251fb0056410fd462a5b8f3244f950e62b5fb2b" } } ], "extra": [ 1, 96, 151, 192, 247, 117, 126, 199, 174, 99, 166, 23, 28, 66, 61, 167, 181, 212, 38, 54, 69, 180, 170, 144, 140, 68, 215, 168, 223, 45, 193, 35, 9, 2, 17, 0, 0, 0, 7, 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