← previous blocknext block →recent activity
Analyzing
Block #97,842,925
12 transactions · 11 stateful · 2026-08-21 06:55:19 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,842,925 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05b82e92…351d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe77a12e0…7be5
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1b7f7926…4ad2
0x34b655…2a6f
2 touches
0 conflicts
0x2560b0ef…aadf
0x34b655…2a6f
2 touches
0 conflicts
0x61817030…47a8
0x34b655…2a6f
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
1 conflict on slot 0x05b82e92aa…da351d
Audit this contract →
← previous block·next block →recent activity