← previous blocknext block →recent activity
Analyzing
Block #94,857,009
13 transactions · 11 stateful · 2026-08-10 19:19:48 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,857,009 · 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1e2f456…7422
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x41dc2b7f…1af1
0x34b655…2a6f
2 touches
0 conflicts
0x41dc2b7f…1af2
0x34b655…2a6f
2 touches
0 conflicts
0x42c27cea…b5f3
0x34b655…2a6f
2 touches
0 conflicts
0x4af8f8d2…0850
0x34b655…2a6f
2 touches
0 conflicts
0x63f46ea6…18c4
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 0xf1e2f45617…f67422
Audit this contract →
← previous block·next block →recent activity