← previous blocknext block →recent activity
Analyzing
Block #93,578,207
10 transactions · 8 stateful · 2026-08-06 07:50:43 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,578,207 · 10 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x830f7d1e…aa4a
0x34b655…2a6f
4 touches
1 conflict
0xbf2145b9…45fe
0x34b655…2a6f
3 touches
1 conflict
0x0db75f00…efa4
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
0x34b655…2a6f
2 touches
0 conflicts
0x19b4e3fd…3821
0x34b655…2a6f
2 touches
0 conflicts
0x1e302fd3…642c
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 0x4e8c4408ae…50d37a
Audit this contract →
← previous block·next block →recent activity