← previous blocknext block →recent activity
Analyzing
Block #93,673,183
9 transactions · 8 stateful · 2026-08-06 15:48:11 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,673,183 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0xc67a220e…c569
0x34b655…2a6f
4 touches
1 conflict
0x0a3e6786…cdaa
0x34b655…2a6f
2 touches
0 conflicts
0x14bb790b…6c37
0x34b655…2a6f
2 touches
0 conflicts
0x157536c0…33ef
0x34b655…2a6f
2 touches
0 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
2 touches
0 conflicts
0x20ae70d6…f262
0x34b655…2a6f
2 touches
0 conflicts
0x46a8a6db…fc86
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x982129521c…f19ba6
Audit this contract →
← previous block·next block →recent activity