← previous blocknext block →recent activity
Analyzing
Block #94,853,171
12 transactions · 11 stateful · 2026-08-10 19:00:30 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,853,171 · 12 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
1w02w13w26w07w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xb3d7f3d4…9459
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
3 touches
1 conflict
0x1368c0ff…46af
0x34b655…2a6f
3 touches
1 conflict
0x2e401ddd…ef19
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
3 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity