← previous blocknext block →recent activity
Analyzing
Block #97,185,774
25 transactions · 16 stateful · 2026-08-18 23:02:02 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,185,774 · 25 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
1w02w03w16w07w010w111w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0x3684bb9c…2e61
0x34b655…2a6f
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x0d838d01…906b
0x34b655…2a6f
4 touches
1 conflict
0x1dafc5cd…f56f
0x34b655…2a6f
4 touches
1 conflict
0x1fa90d39…35c6
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity