← previous blocknext block →recent activity
Analyzing
Block #95,245,004
30 transactions · 16 stateful · 2026-08-12 03:53:23 UTC
Parallelism
83/100
Blocked
69%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,245,004 · 30 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
1w02w13w24w37w18w29w310w422w023w126w227w328w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89b9e5f7…647c
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x09106a95…1467
0x33176b…e078
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x928d962f…f990
0x34b655…2a6f
8 touches
6 conflicts
0xfe480e35…f65e
0x34b655…2a6f
6 touches
3 conflicts
0xdbadf6b0…43b2
0x33176b…e078
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
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 0x89b9e5f72a…b4647c
Audit this contract →
← previous block·next block →recent activity