← previous blocknext block →recent activity
Analyzing
Block #95,123,839
14 transactions · 13 stateful · 2026-08-11 17:42:44 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,123,839 · 14 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
1w02w14w26w38w39w410w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b4aa556…0d2b
0x34b655…2a6f
8 touches
6 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
6 touches
3 conflicts
0x68d69f4f…9444
0x34b655…2a6f
6 touches
3 conflicts
0x35c29640…8779
0x34b655…2a6f
4 touches
1 conflict
0x3f4f9f22…8ad7
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
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
6 conflicts on slot 0x1b4aa556f0…0d0d2b
Audit this contract →
← previous block·next block →recent activity