← previous blocknext block →recent activity
Analyzing
Block #107,813,100
22 transactions · 20 stateful · 2026-09-25 05:46:09 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,813,100 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w010w111w212w313w415w416w517w619w020w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xba522812…1f1f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x3949ab7a…0b85
0x34b655…2a6f
6 touches
3 conflicts
0x2708a370…8b37
0x34b655…2a6f
4 touches
1 conflict
0x2b76a1fb…fdfc
0x34b655…2a6f
4 touches
1 conflict
0x34a6145f…b17d
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity