Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0568ec14a3559b9c1f6f1c91d34989526227f1adc1867661f9ee5904ca2e3f36

Tx prefix hash: 9ff070cf2dce35f20bbed02d430aa25681a965255caa81c9f8a5e6cb751e8254
Tx public key: f36907aedb4f72910ba0f35becce39918ebe689a8fbb280b7ee05fbc3fcf32de
Timestamp: 1634549166 Timestamp [UCT]: 2021-10-18 09:26:06 Age [y:d:h:m:s]: 03:147:13:59:18
Block: 355488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 883245 RingCT/type: yes/0
Extra: 01f36907aedb4f72910ba0f35becce39918ebe689a8fbb280b7ee05fbc3fcf32de02110000000d5d7cc334000000000000000000

1 output(s) for total of 40.749389018000 dcy

stealth address amount amount idx
00: c6eebb785a3c2e114195a5ba860c941c25e9a4cc3110732c7fd19380b51d1c6d 40.749389018000 725722 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": 355498, "vin": [ { "gen": { "height": 355488 } } ], "vout": [ { "amount": 40749389018, "target": { "key": "c6eebb785a3c2e114195a5ba860c941c25e9a4cc3110732c7fd19380b51d1c6d" } } ], "extra": [ 1, 243, 105, 7, 174, 219, 79, 114, 145, 11, 160, 243, 91, 236, 206, 57, 145, 142, 190, 104, 154, 143, 187, 40, 11, 126, 224, 95, 188, 63, 207, 50, 222, 2, 17, 0, 0, 0, 13, 93, 124, 195, 52, 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