← previous blocknext block →recent activity
Analyzing
Block #94,740,695
9 transactions · 8 stateful · 2026-08-10 09:33:45 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,740,695 · 9 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
2w03w14w25w37w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1fa8780…1167
0x34b655…2a6f
8 touches
6 conflicts
0xc6b604e6…5152
0x34b655…2a6f
6 touches
3 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0x1e10796e…6213
0x34b655…2a6f
4 touches
1 conflict
0x1e10796e…6214
0x34b655…2a6f
4 touches
1 conflict
0x2c49e3c2…86c6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
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
6 conflicts on slot 0xb1fa87807f…b41167
Audit this contract →
← previous block·next block →recent activity