← previous blocknext block →recent activity
Analyzing
Block #105,748,657
16 transactions · 16 stateful · 2026-09-18 00:29:35 UTC
Parallelism
56/100
Blocked
63%
Avg conflicts / tx
1.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,748,657 · 16 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
1w02w13w14w25w36w48w210w411w512w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a58d502…385c
0x34b655…2a6f
14 touches
21 conflicts
0x42bfb015…fb28
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6771eae2…7014
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xb64c08c1…2969
0x34b655…2a6f
5 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
21 conflicts on slot 0x2a58d5029f…32385c
Audit this contract →
← previous block·next block →recent activity