← previous blocknext block →recent activity
Analyzing
Block #106,555,141
53 transactions · 50 stateful · 2026-09-20 20:11:01 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,555,141 · 53 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
1w02w13w14w26w013w214w315w316w418w447w148w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53799eb…d928
0x34b655…2a6f
10 touches
10 conflicts
0xa56b5f6e…e64a
0x34b655…2a6f
8 touches
6 conflicts
0xab41643c…f9bf
0x34b655…2a6f
8 touches
6 conflicts
0x04994ed2…9032
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x8f5a38d8…c230
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
10 conflicts on slot 0xc53799ebcf…a9d928
Audit this contract →
← previous block·next block →recent activity