← previous blocknext block →recent activity
Analyzing
Block #105,840,918
21 transactions · 20 stateful · 2026-09-18 08:15:12 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,840,918 · 21 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
2w03w04w18w011w112w013w114w215w316w417w518w619w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x154a3a6d…a391
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x6d5c5d72…914b
0x34b655…2a6f
10 touches
10 conflicts
0x89999c15…fdac
0x34b655…2a6f
10 touches
10 conflicts
0xb50d353f…63e0
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x3018a378…d7bb
0x34b655…2a6f
6 touches
3 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 0x154a3a6def…56a391
Audit this contract →
← previous block·next block →recent activity