← previous blocknext block →recent activity
Analyzing
Block #97,612,686
20 transactions · 20 stateful · 2026-08-20 11:25:03 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,612,686 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w17w28w39w010w311w412w214w415w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88724b87…5e65
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x05ec0ff9…eab5
0x34b655…2a6f
6 touches
3 conflicts
0x47b2d2eb…8aa5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x912b0eb2…bbcd
0x34b655…2a6f
4 touches
1 conflict
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0xb15c58ec…bd83
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 0x88724b8763…1a5e65
Audit this contract →
← previous block·next block →recent activity