Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93a661f846c4f8aa9f24dad78c4cd7afd56610843b42c0ce43199e0f8b9144dc

Tx prefix hash: 605bf4b62682f0cfb8b227c60cab2d371ec3eb950efe74acd085a430a5e71a81
Tx public key: 924b8425bcd84af00f2f952989c625e3b057cb829f615b4c93828a6ce37c9b47
Timestamp: 1696875692 Timestamp [UCT]: 2023-10-09 18:21:32 Age [y:d:h:m:s]: 01:140:05:54:05
Block: 866055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361226 RingCT/type: yes/0
Extra: 01924b8425bcd84af00f2f952989c625e3b057cb829f615b4c93828a6ce37c9b4702110000000975e3f0e9000000000000000000

1 output(s) for total of 0.828705653000 dcy

stealth address amount amount idx
00: d04062163ba60edfb229b31a122187c14bd9d3413bea9207d0597723d3b4917a 0.828705653000 1320623 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": 866065, "vin": [ { "gen": { "height": 866055 } } ], "vout": [ { "amount": 828705653, "target": { "key": "d04062163ba60edfb229b31a122187c14bd9d3413bea9207d0597723d3b4917a" } } ], "extra": [ 1, 146, 75, 132, 37, 188, 216, 74, 240, 15, 47, 149, 41, 137, 198, 37, 227, 176, 87, 203, 130, 159, 97, 91, 76, 147, 130, 138, 108, 227, 124, 155, 71, 2, 17, 0, 0, 0, 9, 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