← previous blocknext block →recent activity
Analyzing
Block #107,785,089
21 transactions · 19 stateful · 2026-09-25 03:25:02 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,785,089 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w19w210w315w016w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x17c93766…889e
0x34b655…2a6f
4 touches
1 conflict
0x2fbf2475…bbc3
0x34b655…2a6f
4 touches
1 conflict
0x3e9bccd1…9cc9
0x34b655…2a6f
4 touches
1 conflict
0x49adc7b7…ff07
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity