Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 475100eda8646339d70b78b5ee68873e115d55c2a70bbd2caa40bd9676396d99

Tx prefix hash: 5b9b5fba60edcbf6109f4bd54328b830250befb56113389ee19054f1bcbbb4dd
Tx public key: 286e21d3b82baa9b88df0449219ae41ef4da512e593661b8dc5cc62b4853dac7
Timestamp: 1726499062 Timestamp [UCT]: 2024-09-16 15:04:22 Age [y:d:h:m:s]: 00:115:21:34:03
Block: 1111439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82871 RingCT/type: yes/0
Extra: 01286e21d3b82baa9b88df0449219ae41ef4da512e593661b8dc5cc62b4853dac7021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ef8beea6b7cc44b383c63949a21c7a82755624b421b9b2e1b7a6562a8e17d39 0.600000000000 1590396 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": 1111449, "vin": [ { "gen": { "height": 1111439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ef8beea6b7cc44b383c63949a21c7a82755624b421b9b2e1b7a6562a8e17d39" } } ], "extra": [ 1, 40, 110, 33, 211, 184, 43, 170, 155, 136, 223, 4, 73, 33, 154, 228, 30, 244, 218, 81, 46, 89, 54, 97, 184, 220, 92, 198, 43, 72, 83, 218, 199, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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