← previous blocknext block →recent activity
Analyzing
Block #97,565,602
16 transactions · 16 stateful · 2026-08-20 07:26:38 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,565,602 · 16 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
2w04w05w16w07w18w19w010w111w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cfec795…7c0e
0x34b655…2a6f
4 touches
1 conflict
0x88ef4184…503b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x49ef2797…8243
0x065c9d…c394
4 touches
1 conflict
0x0d256437…ceb8
0x34b655…2a6f
4 touches
1 conflict
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 0x5cfec7957f…867c0e
Audit this contract →
← previous block·next block →recent activity