Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac65c27de4f33a6cca340b311ebb9e7062595a389ac371e3147d6a6b151b8bf4

Tx prefix hash: 317be7a799958e2be101c9f75e970359c79a0be4061a8aed2960ad253ad979f8
Tx public key: 259bdc7f1fd8f36b3b10d9d45d7531d883e849dfd274876534e234ce61cadc46
Timestamp: 1721384577 Timestamp [UCT]: 2024-07-19 10:22:57 Age [y:d:h:m:s]: 00:271:06:02:58
Block: 1069048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193778 RingCT/type: yes/0
Extra: 01259bdc7f1fd8f36b3b10d9d45d7531d883e849dfd274876534e234ce61cadc4602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2170cf6ebc04c9c25b00915c8d73442b1093ba33869557d3e0bc6aa9ba8ff86f 0.600000000000 1540319 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": 1069058, "vin": [ { "gen": { "height": 1069048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2170cf6ebc04c9c25b00915c8d73442b1093ba33869557d3e0bc6aa9ba8ff86f" } } ], "extra": [ 1, 37, 155, 220, 127, 31, 216, 243, 107, 59, 16, 217, 212, 93, 117, 49, 216, 131, 232, 73, 223, 210, 116, 135, 101, 52, 226, 52, 206, 97, 202, 220, 70, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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