← previous blocknext block →recent activity
Analyzing
Block #108,940,079
23 transactions · 17 stateful · 2026-09-29 04:22:27 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,940,079 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w111w212w318w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0xb3af6b7b…bba9
0x34b655…2a6f
4 touches
1 conflict
0xfc8c9734…8019
0x34b655…2a6f
4 touches
1 conflict
0x238d0a65…428b
0x37db7f…ec7b
4 touches
1 conflict
0xeb1b4ae8…64bd
0x37db7f…ec7b
4 touches
1 conflict
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity