← previous blocknext block →recent activity
Analyzing
Block #105,844,603
24 transactions · 24 stateful · 2026-09-18 08:33:53 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,844,603 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w210w011w112w213w314w415w316w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfce7dfe…5053
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x11506b7a…d05e
0x34b655…2a6f
8 touches
6 conflicts
0xa7189cb8…cd41
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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 0xdfce7dfe53…c75053
Audit this contract →
← previous block·next block →recent activity