← previous blocknext block →recent activity
Analyzing
Block #107,650,663
24 transactions · 23 stateful · 2026-09-24 16:07:14 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,650,663 · 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
1w02w03w15w07w18w29w315w016w117w118w219w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x1abd5c35…67c5
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x2dfc834d…12be
0x34b655…2a6f
4 touches
1 conflict
0x32cfcaed…9b9b
0x34b655…2a6f
4 touches
1 conflict
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x5bd10f19…273b
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity