← previous blocknext block →recent activity
Analyzing
Block #95,527,982
13 transactions · 13 stateful · 2026-08-13 03:49:05 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,527,982 · 13 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
1w02w13w24w05w06w38w19w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac61e67c…0309
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xa46242d8…c0a7
0x34b655…2a6f
4 touches
1 conflict
0xad065451…f5dd
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
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 0xac61e67cea…c80309
Audit this contract →
← previous block·next block →recent activity