Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c002766b961b3289d2cf5ffc346c0c38361a071c029e6381aaed1a7e0f9d36

Tx prefix hash: 67ae5936aa520ee4eb5ff6ba6d3fbd6ece2a69a1cb912831d28a720ada1eddc0
Tx public key: 7ad32e3f54648693f413cf7b41059c8ea612d82a5b27caf5cedd1ceb785e534a
Timestamp: 1644210442 Timestamp [UCT]: 2022-02-07 05:07:22 Age [y:d:h:m:s]: 03:267:15:02:23
Block: 433635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 968525 RingCT/type: yes/0
Extra: 017ad32e3f54648693f413cf7b41059c8ea612d82a5b27caf5cedd1ceb785e534a0211000000032e6b1fd5000000000000000000

1 output(s) for total of 22.448510874000 dcy

stealth address amount amount idx
00: 740b2d64ae7730d418ae36297ef121c6359aea39d3237f58e7505ad696c7ee74 22.448510874000 844350 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": 433645, "vin": [ { "gen": { "height": 433635 } } ], "vout": [ { "amount": 22448510874, "target": { "key": "740b2d64ae7730d418ae36297ef121c6359aea39d3237f58e7505ad696c7ee74" } } ], "extra": [ 1, 122, 211, 46, 63, 84, 100, 134, 147, 244, 19, 207, 123, 65, 5, 156, 142, 166, 18, 216, 42, 91, 39, 202, 245, 206, 221, 28, 235, 120, 94, 83, 74, 2, 17, 0, 0, 0, 3, 46, 107, 31, 213, 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