← previous blocknext block →recent activity
Analyzing
Block #95,204,609
16 transactions · 15 stateful · 2026-08-12 00:28:59 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,204,609 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w17w29w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96dd83e6…a507
0x34b655…2a6f
10 touches
10 conflicts
0x7ee74e97…55f1
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x46aa6403…28e7
0x34b655…2a6f
4 touches
1 conflict
0x934da4f1…43a7
0x34b655…2a6f
4 touches
1 conflict
0x94a421cd…457d
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
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 0x96dd83e650…3fa507
Audit this contract →
← previous block·next block →recent activity