← previous blocknext block →recent activity
Analyzing
Block #106,952,638
27 transactions · 23 stateful · 2026-09-22 05:32:41 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,952,638 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w014w115w216w117w218w319w424w025w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60b6cf89…9374
0x34b655…2a6f
8 touches
6 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0x3edc942f…ef23
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf35dca9e…bd8d
0x1b6862…e19c
4 touches
1 conflict
0x08f9abf1…10bf
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
6 conflicts on slot 0x60b6cf89e4…a49374
Audit this contract →
← previous block·next block →recent activity