← previous blocknext block →recent activity
Analyzing
Block #106,395,107
20 transactions · 20 stateful · 2026-09-20 06:45:34 UTC
Parallelism
55/100
Blocked
55%
Avg conflicts / tx
1.4
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,395,107 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w18w19w310w414w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
10 touches
10 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
8 touches
6 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x2d6ad769…5d2e
0x34b655…2a6f
6 touches
3 conflicts
0x93ec9f85…b586
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
10 conflicts on slot 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity