← previous blocknext block →recent activity
Analyzing
Block #105,932,170
20 transactions · 20 stateful · 2026-09-18 15:55:31 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,932,170 · 20 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
1w02w17w08w110w211w312w413w514w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x315e07b8…9823
0x34b655…2a6f
8 touches
6 conflicts
0x34836ffb…2a0b
0x34b655…2a6f
8 touches
6 conflicts
0x6a23a951…2791
0x34b655…2a6f
8 touches
6 conflicts
0xdb11940a…519b
0x34b655…2a6f
8 touches
6 conflicts
0xdfbcac05…791d
0x34b655…2a6f
6 touches
3 conflicts
0xe796f8b7…ad55
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity