← previous blocknext block →recent activity
Analyzing
Block #97,685,409
9 transactions · 9 stateful · 2026-08-20 17:38:51 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,685,409 · 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
1w02w13w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70f537e8…399b
0x34b655…2a6f
4 touches
1 conflict
0x9de79217…221b
0x34b655…2a6f
4 touches
1 conflict
0x1d9276e8…c282
0x34b655…2a6f
4 touches
1 conflict
0x54023c96…53cf
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc4c059d8…185d
0x34b655…2a6f
4 touches
1 conflict
0xcd5c0ecb…4b5f
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 0x70f537e84a…fa399b
Audit this contract →
← previous block·next block →recent activity