← previous blocknext block →recent activity
Analyzing
Block #105,880,991
24 transactions · 22 stateful · 2026-09-18 11:37:02 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,880,991 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w18w010w312w113w215w016w117w218w321w022w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736b9166…5ea5
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x573e497e…dab5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xadce6355…03bf
0xa6afd3…d132
6 touches
3 conflicts
0x08cf81e6…f097
0xc8689a…ee79
6 touches
3 conflicts
0x9dcfdeae…d1eb
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
6 conflicts on slot 0x736b916691…db5ea5
Audit this contract →
← previous block·next block →recent activity