← previous blocknext block →recent activity
Analyzing
Block #105,843,859
24 transactions · 23 stateful · 2026-09-18 08:30:08 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,843,859 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w213w214w015w116w217w318w419w520w621w723w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
8 touches
6 conflicts
0x4681609f…6493
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x26dddc8a…b005
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity