← previous blocknext block →recent activity
Analyzing
Block #105,881,530
24 transactions · 23 stateful · 2026-09-18 11:39:45 UTC
Parallelism
58/100
Blocked
57%
Avg conflicts / tx
2.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,881,530 · 24 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
1w02w13w17w211w312w413w514w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x297de2d5…7396
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x786d8c6c…a2e7
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x59209c69…415b
0x34b655…2a6f
8 touches
6 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
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
36 conflicts on slot 0x297de2d577…2b7396
Audit this contract →
← previous block·next block →recent activity