← previous blocknext block →recent activity
Analyzing
Block #108,576,471
17 transactions · 17 stateful · 2026-09-27 21:48:25 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
1.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,576,471 · 17 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
1w02w15w06w111w012w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
14 touches
21 conflicts
0xf5dc501b…831c
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd739490d…821e
0x34b655…2a6f
10 touches
10 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
10 touches
10 conflicts
0xc8f8f6c0…0e69
0x34b655…2a6f
7 touches
6 conflicts
0x38734a62…7104
0x34b655…2a6f
6 touches
3 conflicts
0xa05768d5…824e
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: Perpl
21 conflicts on slot 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity