← previous blocknext block →recent activity
Analyzing
Block #93,238,343
30 transactions · 27 stateful · 2026-08-05 03:22:03 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,238,343 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w110w211w115w216w320w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x09106a95…1467
0x33176b…e078
8 touches
6 conflicts
0x15be757a…275e
0x34b655…2a6f
4 touches
1 conflict
0x201d7cf1…f7f2
0x34b655…2a6f
4 touches
1 conflict
0x390dd46c…deef
0x34b655…2a6f
4 touches
1 conflict
0x42c27cea…b5f3
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity