← previous blocknext block →recent activity
Analyzing
Block #106,224,294
26 transactions · 25 stateful · 2026-09-19 16:25:54 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,224,294 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w38w311w417w418w419w520w622w724w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf22f58…5939
0x34b655…2a6f
8 touches
6 conflicts
0x839c0c71…bada
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x2681bf92…a35e
0xd32edf…ff58
7 touches
6 conflicts
0x928d6b23…5374
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x27ee2834…ea9f
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
6 conflicts on slot 0xecf22f58ca…2c5939
Audit this contract →
← previous block·next block →recent activity