← previous blocknext block →recent activity
Analyzing
Block #97,999,034
17 transactions · 14 stateful · 2026-08-21 20:13:00 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,999,034 · 17 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
2w03w04w111w012w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf00bcd…2019
0x34b655…2a6f
4 touches
1 conflict
0x5b7e8e52…6e30
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x6be58ee5…4502
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0xaf30c163…0fb6
0x34b655…2a6f
4 touches
1 conflict
0xb3037bed…6b7c
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
1 conflict on slot 0xfaf00bcd33…4a2019
Audit this contract →
← previous block·next block →recent activity