← previous blocknext block →recent activity
Analyzing
Block #106,053,409
30 transactions · 25 stateful · 2026-09-19 02:05:51 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,053,409 · 30 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
1w04w07w016w119w220w221w122w323w424w525w126w228w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c47b1c…93c8
0x34b655…2a6f
8 touches
6 conflicts
0xcdc81195…034d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
6 touches
3 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0xe530b2cf…6f95
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 0x07c47b1ce2…b693c8
Audit this contract →
← previous block·next block →recent activity