← previous blocknext block →recent activity
Analyzing
Block #107,785,065
16 transactions · 13 stateful · 2026-09-25 03:24:55 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,785,065 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w19w010w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c4
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c5
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c7
0x508254…98bd
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x508254c8…4a98bd
6 conflicts on slot 0x3a663e9a3a…2fa9c4
Audit this contract →
← previous block·next block →recent activity