← previous blocknext block →recent activity
Analyzing
Block #95,157,129
16 transactions · 15 stateful · 2026-08-11 20:30:11 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,157,129 · 16 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
2w09w110w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85167706…718e
0x34b655…2a6f
6 touches
3 conflicts
0xef3f5637…f47c
0x34b655…2a6f
6 touches
3 conflicts
0xb1a14ab5…244f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xcd5c0ecb…4b5f
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d2
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 0x85167706bf…d5718e
Audit this contract →
← previous block·next block →recent activity