← previous blocknext block →recent activity
Analyzing
Block #94,980,760
11 transactions · 11 stateful · 2026-08-11 05:42:12 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,980,760 · 11 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
4w06w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0x19489614…582d
0x34b655…2a6f
4 touches
1 conflict
0x23ef1567…8f31
0x34b655…2a6f
4 touches
1 conflict
0x33b5035a…d1c6
0x34b655…2a6f
4 touches
1 conflict
0x3a51d8ed…0c97
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
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 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity