← previous blocknext block →recent activity
Analyzing
Block #97,987,912
24 transactions · 23 stateful · 2026-08-21 19:16:52 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,987,912 · 24 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
1w02w04w05w06w17w18w29w010w013w117w118w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcc5d8997…432c
0x34b655…2a6f
4 touches
1 conflict
0xe48a389e…557e
0x34b655…2a6f
4 touches
1 conflict
0xeca74ff3…a361
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
1 conflict on slot 0xf85bdc12e0…265dff
Audit this contract →
← previous block·next block →recent activity