← previous blocknext block →recent activity
Analyzing
Block #107,812,930
24 transactions · 23 stateful · 2026-09-25 05:45:18 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,812,930 · 24 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
1w04w05w06w18w010w111w112w113w214w315w316w417w418w522w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa23b9051…392f
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0xbdcfa72b…8436
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
10 conflicts on slot 0xa23b905120…88392f
Audit this contract →
← previous block·next block →recent activity