← previous blocknext block →recent activity
Analyzing
Block #107,785,812
17 transactions · 17 stateful · 2026-09-25 03:28:40 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,785,812 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w19w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaae6463e…bfcc
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x503716b1…f16c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xa0a8c7a5…3422
0x34b655…2a6f
4 touches
1 conflict
0xa9640f62…dd49
0x34b655…2a6f
4 touches
1 conflict
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 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
1 conflict on slot 0xaae6463e2e…b6bfcc
Audit this contract →
← previous block·next block →recent activity