← previous blocknext block →recent activity
Analyzing
Block #97,667,580
23 transactions · 19 stateful · 2026-08-20 16:07:20 UTC
Parallelism
83/100
Blocked
37%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,667,580 · 23 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
2w03w14w26w07w18w29w310w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2e8bece…67d9
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x61a87a98…de3f
0x851145…3f07
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
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
3 conflicts on slot 0xc2e8beced0…cb67d9
Audit this contract →
← previous block·next block →recent activity