← previous blocknext block →recent activity
Analyzing
Block #108,103,038
35 transactions · 29 stateful · 2026-09-26 06:05:27 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,103,038 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w411w512w613w022w024w126w232w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x942b3403…1f40
0x34b655…2a6f
7 touches
6 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd739490d…821e
0x34b655…2a6f
5 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: 0x125f12a1…cda50b
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity