← previous blocknext block →recent activity
Analyzing
Block #108,972,093
17 transactions · 17 stateful · 2026-09-29 07:04:33 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,972,093 · 17 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
1w03w04w15w26w37w48w59w610w713w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe146392e…c808
0x34b655…2a6f
16 touches
28 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
16 touches
28 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
16 touches
28 conflicts
0x238d0a65…428b
0x37db7f…ec7b
16 touches
28 conflicts
0xfc8c9734…8019
0x34b655…2a6f
16 touches
28 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
16 touches
28 conflicts
0xada087b9…4aca
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 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
28 conflicts on slot 0xe146392e30…2ec808
Audit this contract →
← previous block·next block →recent activity