← previous blocknext block →recent activity
Analyzing
Block #94,249,560
10 transactions · 10 stateful · 2026-08-08 16:12:23 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,249,560 · 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
2w03w04w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x7604a8f8…d63a
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xcbb82c6b…c5ea
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x0eb3ab36…88ba
0x34b655…2a6f
2 touches
0 conflicts
0x17c5f614…cfc2
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 0x5d1ac445db…e05233
Audit this contract →
← previous block·next block →recent activity