← previous blocknext block →recent activity
Analyzing
Block #94,251,005
17 transactions · 13 stateful · 2026-08-08 16:19:42 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,251,005 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w19w210w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe60268f6…c562
0x34b655…2a6f
6 touches
3 conflicts
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x3f798539…99c4
0x34b655…2a6f
4 touches
1 conflict
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x5cc0e9c8…3ae6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0xe60268f690…bfc562
Audit this contract →
← previous block·next block →recent activity