← previous blocknext block →recent activity
Analyzing
Block #108,603,525
22 transactions · 21 stateful · 2026-09-28 00:04:36 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,603,525 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w06w18w210w311w413w514w616w221w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x724ba0cf…01c7
0x34b655…2a6f
8 touches
6 conflicts
0x16d77246…bac5
0x34b655…2a6f
6 touches
3 conflicts
0x280aaa58…1c52
0x34b655…2a6f
6 touches
3 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
6 touches
3 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
6 touches
3 conflicts
0x44814729…5910
0x34b655…2a6f
6 touches
3 conflicts
0x52c5428c…9d42
0x34b655…2a6f
6 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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity