← previous blocknext block →recent activity
Analyzing
Block #105,843,576
24 transactions · 23 stateful · 2026-09-18 08:28:42 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,843,576 · 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
1w02w13w210w013w114w215w316w417w518w623w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73d6ce85…d7ce
0x34b655…2a6f
12 touches
15 conflicts
0x9210e826…1414
0x34b655…2a6f
10 touches
10 conflicts
0xdfaa9666…2003
0x34b655…2a6f
10 touches
10 conflicts
0x6d955786…1327
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
10 touches
10 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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 0x73d6ce8531…0ed7ce
Audit this contract →
← previous block·next block →recent activity