← previous blocknext block →recent activity
Analyzing
Block #94,291,150
21 transactions · 18 stateful · 2026-08-08 19:43:02 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,291,150 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w39w411w012w113w214w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xf3383813…4a0c
0x34b655…2a6f
10 touches
10 conflicts
0x4f394483…ff62
0x34b655…2a6f
8 touches
6 conflicts
0x25429022…758c
0x34b655…2a6f
6 touches
3 conflicts
0x70f537e8…399b
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0x7d7ed9e4…4a59
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity