← previous blocknext block →recent activity
Analyzing
Block #95,472,212
16 transactions · 15 stateful · 2026-08-12 23:08:35 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,472,212 · 16 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
1w02w14w05w16w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0c78ade3…f11a
0x34b655…2a6f
4 touches
1 conflict
0x35c29640…8779
0x34b655…2a6f
4 touches
1 conflict
0x3e30f0e6…3720
0x34b655…2a6f
4 touches
1 conflict
0x52f3d91c…1822
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7523c6af…ea66
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity