← previous blocknext block →recent activity
Analyzing
Block #97,820,509
25 transactions · 22 stateful · 2026-08-21 05:01:57 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,820,509 · 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
3w04w17w08w19w010w114w015w118w221w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1eec16a0…9e8c
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x710a044a…20b1
0x34b655…2a6f
6 touches
3 conflicts
0x438f4336…47c9
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x640b1625…b02f
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xac6f24e7…c98b
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 0x1eec16a0d8…3a9e8c
Audit this contract →
← previous block·next block →recent activity