← previous blocknext block →recent activity
Analyzing
Block #108,680,241
19 transactions · 19 stateful · 2026-09-28 06:30:57 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,680,241 · 19 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
1w02w13w24w35w47w08w112w013w114w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x84611dd3…b341
0x1b6862…e19c
10 touches
10 conflicts
0x94b31f77…519d
0xd32edf…ff58
9 touches
10 conflicts
0xe5973e13…68c4
0x1b6862…e19c
8 touches
6 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity