← previous blocknext block →recent activity
Analyzing
Block #94,289,249
13 transactions · 12 stateful · 2026-08-08 19:33:25 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,289,249 · 13 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
4w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cb207c7…638d
0x34b655…2a6f
4 touches
1 conflict
0x64ac7e40…5d7d
0x34b655…2a6f
4 touches
1 conflict
0x71cbd5f6…e66e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x0f240f9c…61eb
0x34b655…2a6f
4 touches
1 conflict
0x0f240f9c…61ea
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
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
1 conflict on slot 0x4cb207c7a4…25638d
Audit this contract →
← previous block·next block →recent activity