← previous blocknext block →recent activity
Analyzing
Block #93,566,070
18 transactions · 17 stateful · 2026-08-06 06:49:42 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,566,070 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w313w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf8d2af…d140
0x34b655…2a6f
8 touches
6 conflicts
0x05b26de9…0fd8
0x34b655…2a6f
4 touches
1 conflict
0x5c0bd1e3…9904
0x40c49f…2af0
4 touches
1 conflict
0x1ead1821…ef11
0x40c49f…2af0
4 touches
1 conflict
0x420b5b92…91ed
0x40c49f…2af0
4 touches
1 conflict
0x20120943…61ad
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x1bf8d2afa1…d2d140
Audit this contract →
← previous block·next block →recent activity