← previous blocknext block →recent activity
Analyzing
Block #108,021,295
54 transactions · 40 stateful · 2026-09-25 23:14:07 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
1.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,021,295 · 54 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w08w215w217w119w220w321w327w437w538w541w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0xda7ee0fc…51f2
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x5f77d607…2c84
0x065c9d…c394
10 touches
10 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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity