← previous blocknext block →recent activity
Analyzing
Block #107,814,258
21 transactions · 20 stateful · 2026-09-25 05:51:59 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,814,258 · 21 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
2w010w111w012w113w214w115w316w417w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7fff095…7a34
0x34b655…2a6f
10 touches
10 conflicts
0xba522812…1f1f
0x34b655…2a6f
10 touches
10 conflicts
0x2130a548…c1de
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x4611acd1…c536
0x34b655…2a6f
6 touches
3 conflicts
0x87b3c188…6ea2
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 0xd7fff095f0…0d7a34
Audit this contract →
← previous block·next block →recent activity