← previous blocknext block →recent activity
Analyzing
Block #94,720,379
57 transactions · 54 stateful · 2026-08-10 07:51:01 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,720,379 · 57 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
4w05w16w27w311w052w154w455w556w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c16527f…628c
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x41377979…0a18
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0x22b7f6e6…63a7
0x34b655…2a6f
4 touches
1 conflict
0x58b6dfdc…67c8
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
15 conflicts on slot 0x5c16527f85…5b628c
Audit this contract →
← previous block·next block →recent activity