← previous blocknext block →recent activity
Analyzing
Block #94,790,219
20 transactions · 19 stateful · 2026-08-10 13:43:47 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,790,219 · 20 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
1w02w13w04w05w16w17w210w311w412w413w514w116w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x428b6e5b…8909
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x36cf7d70…f333
0x34b655…2a6f
4 touches
1 conflict
0x5ddf85a7…78c8
0x34b655…2a6f
4 touches
1 conflict
0x66182b56…8db0
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
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 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity