← previous blocknext block →recent activity
Analyzing
Block #97,512,652
17 transactions · 16 stateful · 2026-08-20 02:58:49 UTC
Parallelism
82/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,512,652 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w011w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x07fc9af5…cfb9
0x34b655…2a6f
4 touches
1 conflict
0x1a870a73…5814
0x34b655…2a6f
4 touches
1 conflict
0x793a0084…fe67
0x34b655…2a6f
3 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
2 touches
0 conflicts
0x0b54bd50…bb67
0x34b655…2a6f
2 touches
0 conflicts
0x0bbe6742…e34a
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity