← previous blocknext block →recent activity
Analyzing
Block #108,113,062
24 transactions · 23 stateful · 2026-09-26 06:55:54 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,113,062 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w111w212w316w020w021w122w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x7efbf74f…f9d2
0x34b655…2a6f
6 touches
3 conflicts
0x92f687cb…c1db
0x34b655…2a6f
6 touches
3 conflicts
0x7aa463de…e7b8
0x34b655…2a6f
4 touches
1 conflict
0xd3d054d7…4bfb
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