← previous blocknext block →recent activity
Analyzing
Block #105,626,088
24 transactions · 21 stateful · 2026-09-17 14:12:40 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,626,088 · 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
1w02w03w14w05w06w17w210w115w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a719b1d…365f
0x34b655…2a6f
8 touches
6 conflicts
0x544745e8…d72e
0x34b655…2a6f
6 touches
3 conflicts
0xa1c8595d…183f
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4bdc0194…bf15
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8f84702c…c5f9
0x34b655…2a6f
4 touches
1 conflict
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 0x2a719b1dc4…7d365f
Audit this contract →
← previous block·next block →recent activity