← previous blocknext block →recent activity
Analyzing
Block #97,496,396
6 transactions · 6 stateful · 2026-08-20 01:37:02 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,496,396 · 6 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0xa1350032…537b
0x34b655…2a6f
4 touches
1 conflict
0x015a51cb…b7b7
0x34b655…2a6f
4 touches
1 conflict
0x01c394b9…b88c
0x34b655…2a6f
2 touches
0 conflicts
0x06661beb…fb9b
0x34b655…2a6f
2 touches
0 conflicts
0x13e2f506…7d16
0x34b655…2a6f
2 touches
0 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x180785e9…5e74
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 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity