← previous blocknext block →recent activity
Analyzing
Block #95,371,767
19 transactions · 19 stateful · 2026-08-12 14:41:44 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,371,767 · 19 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
3w04w16w17w29w013w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fab7fbe…1ce5
0x34b655…2a6f
6 touches
3 conflicts
0x74137b07…5880
0x34b655…2a6f
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0x46346c28…1297
0x34b655…2a6f
4 touches
1 conflict
0x4b80417b…75c3
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x68f434c6…a86f
0x34b655…2a6f
4 touches
1 conflict
0x7a8cad7f…48cd
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 0x5fab7fbe22…391ce5
Audit this contract →
← previous block·next block →recent activity