← previous blocknext block →recent activity
Analyzing
Block #108,397,307
18 transactions · 17 stateful · 2026-09-27 06:46:22 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,397,307 · 18 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
1w02w13w210w312w315w416w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
10 touches
10 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0xbc5c1743…052c
0x34b655…2a6f
10 touches
10 conflicts
0x69267d59…b68e
0xd32edf…ff58
9 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x6d5d1fb5…86a7
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
10 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity