← previous blocknext block →recent activity
Analyzing
Block #108,610,252
37 transactions · 36 stateful · 2026-09-28 00:38:29 UTC
Parallelism
76/100
Blocked
61%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,610,252 · 37 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w07w18w210w112w213w314w015w119w320w121w022w123w224w325w426w527w629w231w432w534w736w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x232b0b19…d946
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 conflicts
0xfa2794a8…40de
0x34b655…2a6f
8 touches
6 conflicts
0x46c14e01…ff09
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity