← previous blocknext block →recent activity
Analyzing
Block #93,437,519
20 transactions · 19 stateful · 2026-08-05 20:03:29 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,437,519 · 20 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
2w04w05w17w18w09w010w111w216w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b157552…a138
0x968279…9342
6 touches
3 conflicts
0x1b157552…a139
0x968279…9342
6 touches
3 conflicts
0x1b157552…a13c
0x968279…9342
6 touches
3 conflicts
0x1b157552…a13d
0x968279…9342
6 touches
3 conflicts
0x1b157552…a13f
0x968279…9342
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
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: 0x96827978…f09342
3 conflicts on slot 0x1b15755200…90a138
Audit this contract →
← previous block·next block →recent activity