← previous blocknext block →recent activity
Analyzing
Block #95,654,933
17 transactions · 16 stateful · 2026-08-13 14:27:38 UTC
Parallelism
76/100
Blocked
19%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,654,933 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x468d132a…d7b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xfb67be15…a190
0x34b655…2a6f
6 touches
3 conflicts
0x92a04045…f73d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4af8f8d2…0850
0x34b655…2a6f
4 touches
1 conflict
0x81a169fb…d227
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 0x468d132ac7…d0d7b8
Audit this contract →
← previous block·next block →recent activity