← previous blocknext block →recent activity
Analyzing
Block #105,843,132
32 transactions · 31 stateful · 2026-09-18 08:26:27 UTC
Parallelism
66/100
Blocked
48%
Avg conflicts / tx
1.66
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,843,132 · 32 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
2w05w010w011w112w213w314w417w121w222w323w324w426w528w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
8 touches
6 conflicts
0x342dbb0b…1b19
0x34b655…2a6f
6 touches
3 conflicts
0x70d81211…f49f
0x34b655…2a6f
6 touches
3 conflicts
0xb545a135…c026
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity