← previous blocknext block →recent activity
Analyzing
Block #97,665,858
16 transactions · 16 stateful · 2026-08-20 15:58:28 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,665,858 · 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
1w02w13w06w07w110w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca5aad0a…0fce
0x34b655…2a6f
4 touches
1 conflict
0x9dd37003…3b83
0xe1c8b7…3022
4 touches
1 conflict
0x962f9067…c207
0xb0a788…7777
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x843d1c63…21ce
0x91b81b…6d56
4 touches
1 conflict
0x82d396a1…2adb
0x91b81b…6d56
4 touches
1 conflict
0x01ad188c…9b7f
0x91b81b…6d56
4 touches
1 conflict
0x00000000…0004
0x65d862…09f4
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 0xca5aad0a81…b90fce
Audit this contract →
← previous block·next block →recent activity