← previous blocknext block →recent activity
Analyzing
Block #105,855,960
18 transactions · 18 stateful · 2026-09-18 09:31:04 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,855,960 · 18 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
1w02w07w08w19w210w311w412w513w616w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2560305…f27d
0x34b655…2a6f
10 touches
10 conflicts
0x33416595…47c0
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0x297de2d5…7396
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
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
10 conflicts on slot 0xb256030504…6df27d
Audit this contract →
← previous block·next block →recent activity