← previous blocknext block →recent activity
Analyzing
Block #95,904,953
20 transactions · 17 stateful · 2026-08-14 11:26:25 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,904,953 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w211w312w014w015w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
6 touches
3 conflicts
0xeea20776…5c2f
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xa33e4ca4…e6c7
0x34b655…2a6f
4 touches
1 conflict
0xb856a9e9…9da3
0x34b655…2a6f
4 touches
1 conflict
0xd4230a60…bd13
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
10 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity