← previous blocknext block →recent activity
Analyzing
Block #105,841,695
19 transactions · 19 stateful · 2026-09-18 08:19:08 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,841,695 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w010w111w212w313w414w015w117w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x8ae87135…d426
0x34b655…2a6f
8 touches
6 conflicts
0x5684aadd…8d62
0x34b655…2a6f
8 touches
6 conflicts
0x3492a206…c5c6
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
6 touches
3 conflicts
0x693badd1…0fa5
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity