← previous blocknext block →recent activity
Analyzing
Block #107,817,160
39 transactions · 34 stateful · 2026-09-25 06:06:35 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #107,817,160 · 39 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w07w18w210w014w115w218w321w022w223w324w425w526w627w728w636w837w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
12 touches
15 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x93e9d6dc…6aea
0x34b655…2a6f
6 touches
3 conflicts
0xcdc80ccc…38e6
0xd32edf…ff58
5 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
15 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity