← previous blocknext block →recent activity
Analyzing
Block #97,665,809
14 transactions · 13 stateful · 2026-08-20 15:58:13 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,665,809 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c089c67…f76c
0x34b655…2a6f
4 touches
1 conflict
0xd7695391…fee5
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x02b4abec…397d
0x34b655…2a6f
2 touches
0 conflicts
0x0398c745…05d0
0x34b655…2a6f
2 touches
0 conflicts
0x10ae1a9b…bf3e
0x34b655…2a6f
2 touches
0 conflicts
0x25957369…c648
0x34b655…2a6f
2 touches
0 conflicts
0x2afbb327…04fd
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 0x0c089c6707…1af76c
Audit this contract →
← previous block·next block →recent activity