← previous blocknext block →recent activity
Analyzing
Block #94,675,822
18 transactions · 15 stateful · 2026-08-10 04:06:54 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,675,822 · 18 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
2w04w05w16w27w08w112w313w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
10 touches
10 conflicts
0xaf65c4a2…4000
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x4dee3f71…642a
0x34b655…2a6f
4 touches
1 conflict
0x5500f593…a813
0x34b655…2a6f
4 touches
1 conflict
0x672d0226…debc
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
10 conflicts on slot 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity