← previous blocknext block →recent activity
Analyzing
Block #97,553,539
9 transactions · 9 stateful · 2026-08-20 06:25:04 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,553,539 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x1dc86774…166a
0x34b655…2a6f
4 touches
1 conflict
0x8902ba1f…f4b6
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9284
0x2b46c0…1669
2 touches
0 conflicts
0x2f74f175…9285
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity