← previous blocknext block →recent activity
Analyzing
Block #105,582,124
12 transactions · 9 stateful · 2026-09-17 10:31:20 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,582,124 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b7caca8…860f
0x34b655…2a6f
4 touches
1 conflict
0x8e33015d…b134
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xb0f5bc30…5d12
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xffdc4ab0…9626
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
2 touches
0 conflicts
0x34f8df0b…ad11
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x2b7caca849…39860f
Audit this contract →
← previous block·next block →recent activity