← previous blocknext block →recent activity
Analyzing
Block #97,567,730
21 transactions · 17 stateful · 2026-08-20 07:37:29 UTC
Parallelism
90/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,567,730 · 21 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
1w04w010w111w012w013w117w019w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96ba3f59…db68
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xea1d91a3…b583
0x34b655…2a6f
4 touches
1 conflict
0x22414fbb…1edf
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8caf8776…b148
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 0x96ba3f594f…1cdb68
Audit this contract →
← previous block·next block →recent activity