← previous blocknext block →recent activity
Analyzing
Block #107,651,169
19 transactions · 19 stateful · 2026-09-24 16:09:47 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,651,169 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w27w09w010w111w114w015w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ba83b5…d0a8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaf7f13f9…a2c9
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x097cee83…0878
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x4887bd94…d87b
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
3 conflicts on slot 0xa7ba83b5e1…e4d0a8
Audit this contract →
← previous block·next block →recent activity