← previous blocknext block →recent activity
Analyzing
Block #95,193,813
18 transactions · 14 stateful · 2026-08-11 23:34:41 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,193,813 · 18 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
1w04w05w18w09w110w211w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42e917f7…ed8c
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 conflicts
0x7b179be5…a40a
0x34b655…2a6f
4 touches
1 conflict
0x1a69c7c5…09cc
0x34b655…2a6f
4 touches
1 conflict
0x3111bd38…5f2e
0x34b655…2a6f
4 touches
1 conflict
0xb77363ff…ace7
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 0x42e917f7fa…e0ed8c
Audit this contract →
← previous block·next block →recent activity