← previous blocknext block →recent activity
Analyzing
Block #94,815,703
20 transactions · 19 stateful · 2026-08-10 15:52:00 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,815,703 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w18w29w311w412w413w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x772ab420…c2f6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x62d597df…516e
0x34b655…2a6f
4 touches
1 conflict
0x9577c5b8…b791
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9293
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 0x772ab420dc…dcc2f6
Audit this contract →
← previous block·next block →recent activity