← previous blocknext block →recent activity
Analyzing
Block #93,231,077
11 transactions · 11 stateful · 2026-08-05 02:45:32 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,231,077 · 11 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
1w02w04w15w26w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x231ccc13…a7c6
0x34b655…2a6f
8 touches
6 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
6 touches
3 conflicts
0x3550075a…fb0f
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
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 0x231ccc1338…7fa7c6
Audit this contract →
← previous block·next block →recent activity