← previous blocknext block →recent activity
Analyzing
Block #107,813,255
28 transactions · 23 stateful · 2026-09-25 05:46:56 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,813,255 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w311w013w215w316w417w519w621w722w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc64d3656…0c1c
0x34b655…2a6f
12 touches
15 conflicts
0xba522812…1f1f
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x34a6145f…b17d
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
8 touches
6 conflicts
0x48203298…65cb
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
15 conflicts on slot 0xc64d3656b5…c50c1c
Audit this contract →
← previous block·next block →recent activity