← previous blocknext block →recent activity
Analyzing
Block #93,921,869
20 transactions · 18 stateful · 2026-08-07 12:38:52 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,921,869 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w010w111w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ecac9ec…0d2d
0xe52b14…7230
12 touches
15 conflicts
0x9c70dec2…1719
0xe52b14…7230
12 touches
15 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x77550e63…2cbe
0xe52b14…7230
12 touches
15 conflicts
0x77550e63…2cc0
0xe52b14…7230
12 touches
15 conflicts
0x9b2d3bee…8eeb
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
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: 0xe52b1424…bb7230
15 conflicts on slot 0x5ecac9ec9e…6d0d2d
Audit this contract →
← previous block·next block →recent activity