← previous blocknext block →recent activity
Analyzing
Block #107,817,452
36 transactions · 34 stateful · 2026-09-25 06:08:03 UTC
Parallelism
53/100
Blocked
65%
Avg conflicts / tx
2.5
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #107,817,452 · 36 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w012w313w114w215w316w417w518w619w720w821w922w1024w1226w1428w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0x7031898f…7365
0x34b655…2a6f
12 touches
15 conflicts
0x711ceb8d…5202
0x34b655…2a6f
10 touches
10 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
10 touches
10 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
10 touches
10 conflicts
0xfd2f61b3…a8bc
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity