← previous blocknext block →recent activity
Analyzing
Block #94,951,358
16 transactions · 14 stateful · 2026-08-11 03:14:20 UTC
Parallelism
69/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,951,358 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0xfaf08ba6…f2d9
0x34b655…2a6f
3 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
3 touches
1 conflict
0x6743bc9f…1ed0
0x34b655…2a6f
2 touches
0 conflicts
0x88fec46a…81d0
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
6 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity