← previous blocknext block →recent activity
Analyzing
Block #93,923,986
18 transactions · 18 stateful · 2026-08-07 12:49:31 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,923,986 · 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
2w03w04w15w26w29w310w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53838dd…85c9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4e621c19…6089
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e65
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xff68510a…09f1
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e66
0x34b655…2a6f
6 touches
3 conflicts
0x875d9d25…f692
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 0xc53838ddd7…b885c9
Audit this contract →
← previous block·next block →recent activity