← previous blocknext block →recent activity
Analyzing
Block #94,685,004
13 transactions · 11 stateful · 2026-08-10 04:53:06 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,685,004 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0a2300ab…81c7
0x34b655…2a6f
2 touches
0 conflicts
0x168f75b5…b2d1
0x34b655…2a6f
2 touches
0 conflicts
0x19ebfd29…e80e
0x34b655…2a6f
2 touches
0 conflicts
0x33d4fbe3…a782
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 0xe2e52e4663…6f0894
Audit this contract →
← previous block·next block →recent activity