← previous blocknext block →recent activity
Analyzing
Block #107,824,046
23 transactions · 21 stateful · 2026-09-25 06:41:15 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,824,046 · 23 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
1w02w13w25w06w17w09w310w212w014w115w316w417w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ba83b5…d0a8
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x232b0b19…d946
0x34b655…2a6f
6 touches
3 conflicts
0x3d24f8e0…5ab3
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
6 touches
3 conflicts
0x4a1553d9…655d
0x34b655…2a6f
6 touches
3 conflicts
0x9ad325f5…cc43
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 0xa7ba83b5e1…e4d0a8
Audit this contract →
← previous block·next block →recent activity