← previous blocknext block →recent activity
Analyzing
Block #105,608,214
17 transactions · 17 stateful · 2026-09-17 12:42:40 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,608,214 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w010w011w112w013w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ecbbe7…f713
0x34b655…2a6f
6 touches
3 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
4 touches
1 conflict
0xb3e108b2…d517
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x48132b64…8e95
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 0xa7ecbbe767…04f713
Audit this contract →
← previous block·next block →recent activity