← previous blocknext block →recent activity
Analyzing
Block #102,874,670
39 transactions · 33 stateful · 2026-09-07 22:38:51 UTC
Parallelism
80/100
Blocked
64%
Avg conflicts / tx
1.51
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,874,670 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w08w09w110w216w118w220w122w326w327w428w529w630w631w136w537w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x820d7282…6c34
0x34b655…2a6f
10 touches
10 conflicts
0x354e383e…817c
0xa6afd3…d132
10 touches
10 conflicts
0x9d929e0c…9421
0xa6afd3…d132
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x737acb78…fce8
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity