← previous blocknext block →recent activity
Analyzing
Block #97,547,175
17 transactions · 15 stateful · 2026-08-20 05:52:28 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,547,175 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w17w28w310w312w013w114w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38a1e34…37c3
0x34b655…2a6f
8 touches
6 conflicts
0xf9a57445…8ac2
0x34b655…2a6f
6 touches
3 conflicts
0x9d4716b5…3dd9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0xc38a1e3492…2d37c3
Audit this contract →
← previous block·next block →recent activity