← previous blocknext block →recent activity
Analyzing
Block #93,505,935
16 transactions · 15 stateful · 2026-08-06 01:47:25 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,505,935 · 16 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
1w02w13w26w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33366bcb…32b0
0x34b655…2a6f
8 touches
6 conflicts
0xe9155399…bba2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbf1713bb…f582
0xd32edf…ff58
5 touches
3 conflicts
0x87d62b39…b5ab
0x34b655…2a6f
4 touches
1 conflict
0x35c29640…8779
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 0x33366bcbf2…de32b0
Audit this contract →
← previous block·next block →recent activity