← previous blocknext block →recent activity
Analyzing
Block #106,539,572
36 transactions · 33 stateful · 2026-09-20 18:52:40 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.28
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,539,572 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w08w09w110w213w114w216w324w125w226w328w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
12 touches
15 conflicts
0x76ed17bf…9bd8
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x0c0ca07f…b78d
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x64ca604a…e7fe
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
15 conflicts on slot 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity