← previous blocknext block →recent activity
Analyzing
Block #107,817,154
24 transactions · 19 stateful · 2026-09-25 06:06:33 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,817,154 · 24 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
2w03w16w27w38w09w110w011w112w213w114w316w422w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ee34d1…30f8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x49570407…8583
0x34b655…2a6f
8 touches
6 conflicts
0x641aed07…bcb9
0x34b655…2a6f
8 touches
6 conflicts
0xc7679110…572d
0x34b655…2a6f
6 touches
3 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x69ee34d107…a730f8
Audit this contract →
← previous block·next block →recent activity