← previous blocknext block →recent activity
Analyzing
Block #107,785,929
24 transactions · 24 stateful · 2026-09-25 03:29:16 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,785,929 · 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
1w03w04w17w08w111w213w014w115w116w217w321w322w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bd71786…2d83
0x34b655…2a6f
8 touches
6 conflicts
0x2561ae0a…6826
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x594bcf34…56d0
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x46c14e01…ff09
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 0x2bd7178683…a02d83
Audit this contract →
← previous block·next block →recent activity