← previous blocknext block →recent activity
Analyzing
Block #94,486,419
8 transactions · 6 stateful · 2026-08-09 12:14:17 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,486,419 · 8 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x232f95c2…1d16
0x34b655…2a6f
4 touches
1 conflict
0x2bc437df…a6c7
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x1bb56de3…732e
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbed17…4f3b
0x34b655…2a6f
2 touches
0 conflicts
0x1ffbed17…4f3c
0x34b655…2a6f
2 touches
0 conflicts
0x21280422…0930
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity