← previous blocknext block →recent activity
Analyzing
Block #106,423,317
31 transactions · 27 stateful · 2026-09-20 09:07:31 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
2.48
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,423,317 · 31 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
2w03w14w25w312w414w220w521w622w724w825w926w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cd9fd28…a158
0x34b655…2a6f
18 touches
36 conflicts
0x05b1f4af…b126
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x48203298…65cb
0x34b655…2a6f
10 touches
10 conflicts
0xe66c119a…b022
0x34b655…2a6f
10 touches
10 conflicts
0x0490581d…adaf
0x34b655…2a6f
10 touches
10 conflicts
0xedf0fd5d…0c8b
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x7cd9fd286f…a7a158
Audit this contract →
← previous block·next block →recent activity