← previous blocknext block →recent activity
Analyzing
Block #93,359,637
17 transactions · 16 stateful · 2026-08-05 13:31:54 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,359,637 · 17 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
1w03w04w16w27w38w410w514w015w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x75aa78e1…2176
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
8 touches
6 conflicts
0x216ffe66…1f94
0x34b655…2a6f
8 touches
6 conflicts
0xac3e4969…39e9
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: Perpl
10 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity