← previous blocknext block →recent activity
Analyzing
Block #93,843,440
15 transactions · 13 stateful · 2026-08-07 06:04:07 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,843,440 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w18w210w011w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x05ad0597…856d
0x34b655…2a6f
6 touches
3 conflicts
0x17c93766…889e
0x34b655…2a6f
4 touches
1 conflict
0x22bef947…cc48
0x34b655…2a6f
4 touches
1 conflict
0x241ca014…4529
0x34b655…2a6f
4 touches
1 conflict
0x2a0c0a9c…5ea2
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x3a5d6372…34cd
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
3 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity