← previous blocknext block →recent activity
Analyzing
Block #106,397,682
25 transactions · 25 stateful · 2026-09-20 06:58:31 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,397,682 · 25 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
2w03w14w08w010w112w214w315w417w119w220w421w523w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b4318f0…78fb
0x34b655…2a6f
12 touches
15 conflicts
0x3b53436c…2ec3
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
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
15 conflicts on slot 0x1b4318f096…f178fb
Audit this contract →
← previous block·next block →recent activity