← previous blocknext block →recent activity
Analyzing
Block #106,216,993
13 transactions · 11 stateful · 2026-09-19 15:49:09 UTC
Parallelism
54/100
Blocked
55%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,216,993 · 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
1w02w03w14w25w36w410w011w112w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99856c4…370d
0x34b655…2a6f
10 touches
10 conflicts
0x28508e20…5783
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0xb0e1ec3a…aa94
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x469dac8d…3411
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 0xf99856c491…9a370d
Audit this contract →
← previous block·next block →recent activity