← previous blocknext block →recent activity
Analyzing
Block #97,998,242
21 transactions · 21 stateful · 2026-08-21 20:09:00 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,998,242 · 21 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
2w03w04w05w18w112w213w214w315w018w119w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61ca6437…2142
0x34b655…2a6f
8 touches
6 conflicts
0xc45e4fb5…7cc3
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x68106229…7057
0xa6afd3…d132
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc6d445ec…8564
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 0x61ca6437ec…412142
Audit this contract →
← previous block·next block →recent activity