← previous blocknext block →recent activity
Analyzing
Block #107,816,668
29 transactions · 23 stateful · 2026-09-25 06:04:07 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,816,668 · 29 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
1w03w04w05w06w17w19w210w311w012w213w314w415w525w026w127w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x013bb37b…eb50
0x1b6862…e19c
6 touches
3 conflicts
0xc7679110…572d
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x3916beef…0978
0x34b655…2a6f
6 touches
3 conflicts
0xd327dda0…d8ed
0xd32edf…ff58
5 touches
3 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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity