← previous blocknext block →recent activity
Analyzing
Block #108,671,530
54 transactions · 39 stateful · 2026-09-28 05:47:06 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.46
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #108,671,530 · 54 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w011w114w218w119w220w321w432w333w551w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xa51b4fd3…b942
0xd32edf…ff58
11 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x7dd96c96…7335
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
8 touches
6 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
8 touches
6 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity