← previous blocknext block →recent activity
Analyzing
Block #97,535,631
17 transactions · 10 stateful · 2026-08-20 04:54:24 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,535,631 · 17 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
2w05w06w17w28w09w114w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc136c1d…4731
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7a3d8d07…84de
0x34b655…2a6f
4 touches
1 conflict
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf607560e…828a
0x34b655…2a6f
4 touches
1 conflict
0x1dc86774…166a
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 0xdc136c1de3…1a4731
Audit this contract →
← previous block·next block →recent activity