← previous blocknext block →recent activity
Analyzing
Block #93,922,005
23 transactions · 17 stateful · 2026-08-07 12:39:33 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,922,005 · 23 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
1w02w16w07w08w19w210w311w412w513w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x58733c38…f2cd
0xe52b14…7230
6 touches
3 conflicts
0xc0fe633f…443a
0xe52b14…7230
6 touches
3 conflicts
0xc4a2f619…eb38
0xe52b14…7230
6 touches
3 conflicts
0xd4e69a1d…6139
0xe52b14…7230
6 touches
3 conflicts
0xee8defd7…73c4
0xe52b14…7230
6 touches
3 conflicts
0xef7c06bc…c2eb
0xe52b14…7230
6 touches
3 conflicts
0x09e0690d…6e3d
0xe52b14…7230
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: 0xe52b1424…bb7230
15 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity