← previous blocknext block →recent activity
Analyzing
Block #97,535,721
17 transactions · 15 stateful · 2026-08-20 04:54:51 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,535,721 · 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
1w03w07w08w110w013w115w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x897ffc67…7660
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x015a51cb…b7b7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x1f8ecef7…5af3
0x34b655…2a6f
2 touches
0 conflicts
0x25d909da…1722
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 0x897ffc67fc…ea7660
Audit this contract →
← previous block·next block →recent activity