← previous blocknext block →recent activity
Analyzing
Block #97,671,606
30 transactions · 19 stateful · 2026-08-20 16:28:05 UTC
Parallelism
93/100
Blocked
32%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,671,606 · 30 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
4w010w112w016w017w018w019w123w024w126w027w128w129w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x753fbaca…6be4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbb4fd99a…afa6
0x34b655…2a6f
4 touches
1 conflict
0xb4a95e21…8ec7
0x34b655…2a6f
4 touches
1 conflict
0xb2560305…f27d
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
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 0x753fbaca2b…706be4
Audit this contract →
← previous block·next block →recent activity