← previous blocknext block →recent activity
Analyzing
Block #97,682,914
24 transactions · 21 stateful · 2026-08-20 17:26:11 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,682,914 · 24 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
4w05w16w07w18w211w012w113w014w315w222w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f01765…9b35
0x34b655…2a6f
6 touches
3 conflicts
0xb7b446d2…2006
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2ed00f98…da9f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b9346b3…8dcb
0x34b655…2a6f
4 touches
1 conflict
0x736c5b69…fb3f
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 0xb5f0176510…ee9b35
Audit this contract →
← previous block·next block →recent activity