← previous blocknext block →recent activity
Analyzing
Block #108,351,295
18 transactions · 17 stateful · 2026-09-27 02:54:50 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,351,295 · 18 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
1w07w08w111w212w313w414w515w616w717w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
16 touches
28 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd739490d…821e
0x34b655…2a6f
11 touches
15 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
10 touches
10 conflicts
0x425d7470…3007
0x34b655…2a6f
9 touches
10 conflicts
0xc166a323…1f33
0x34b655…2a6f
6 touches
3 conflicts
0x26f84fa9…d378
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
28 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity