← previous blocknext block →recent activity
Analyzing
Block #107,848,660
22 transactions · 19 stateful · 2026-09-25 08:45:08 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,848,660 · 22 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
2w03w14w05w19w010w111w212w313w414w515w616w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecff7c35…1b43
0x34b655…2a6f
14 touches
21 conflicts
0xbb60956a…390c
0x34b655…2a6f
14 touches
21 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
12 touches
15 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
10 touches
10 conflicts
0xb3d828cf…a9b8
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcd232ca9…031a
0x34b655…2a6f
6 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 0xecff7c3510…111b43
Audit this contract →
← previous block·next block →recent activity