← previous blocknext block →recent activity
Analyzing
Block #107,815,028
28 transactions · 25 stateful · 2026-09-25 05:55:51 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,815,028 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w112w015w116w018w119w220w321w424w225w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x740fff9f…4244
0x34b655…2a6f
10 touches
10 conflicts
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0ebd14d0…bbd1
0x34b655…2a6f
6 touches
3 conflicts
0x4ac770b4…8b4c
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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity