← previous blocknext block →recent activity
Analyzing
Block #108,515,200
19 transactions · 17 stateful · 2026-09-27 16:39:50 UTC
Parallelism
58/100
Blocked
59%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,515,200 · 19 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
5w06w17w28w39w110w011w212w313w414w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cb7ee74…b8a5
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xe8afe685…f531
0x34b655…2a6f
8 touches
6 conflicts
0x2ee6016f…be0f
0x34b655…2a6f
6 touches
3 conflicts
0x5900e8aa…2391
0x34b655…2a6f
6 touches
3 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x3394b067…b230
0x34b655…2a6f
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
10 conflicts on slot 0x3cb7ee74c7…7db8a5
Audit this contract →
← previous block·next block →recent activity