← previous blocknext block →recent activity
Analyzing
Block #95,112,903
16 transactions · 15 stateful · 2026-08-11 16:47:44 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.88
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,112,903 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w07w18w09w111w212w113w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x612a8656…e330
0x34b655…2a6f
5 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x312c6e56…3d7a
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
3 conflicts on slot 0x4e58deff76…56c5d0
Audit this contract →
← previous block·next block →recent activity