← previous blocknext block →recent activity
Analyzing
Block #94,279,082
13 transactions · 11 stateful · 2026-08-08 18:41:58 UTC
Parallelism
54/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,279,082 · 13 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
1w02w03w16w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcd33fd9e…dcc1
0x34b655…2a6f
6 touches
3 conflicts
0x76a66a12…3513
0x34b655…2a6f
4 touches
1 conflict
0x775bacba…73e5
0x34b655…2a6f
4 touches
1 conflict
0xacbb7947…8807
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 0xc824469a90…af6426
Audit this contract →
← previous block·next block →recent activity