← previous blocknext block →recent activity
Analyzing
Block #106,931,883
30 transactions · 30 stateful · 2026-09-22 03:48:13 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
1.43
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,931,883 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w48w510w211w612w713w814w915w1017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04994ed2…9032
0x34b655…2a6f
14 touches
21 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x69168e33…6e1f
0x34b655…2a6f
12 touches
15 conflicts
0x743f0e02…73ec
0x34b655…2a6f
12 touches
15 conflicts
0x26799298…9ff2
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
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
21 conflicts on slot 0x04994ed232…129032
Audit this contract →
← previous block·next block →recent activity