← previous blocknext block →recent activity
Analyzing
Block #108,020,742
33 transactions · 31 stateful · 2026-09-25 23:11:20 UTC
Parallelism
73/100
Blocked
65%
Avg conflicts / tx
1.94
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,020,742 · 33 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
2w03w17w08w19w010w111w212w313w415w516w217w419w320w426w629w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x1e393384…1d24
0x34b655…2a6f
10 touches
10 conflicts
0x9b88924e…aaee
0xd32edf…ff58
9 touches
10 conflicts
0x49cf5413…f268
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 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity