← previous blocknext block →recent activity
Analyzing
Block #97,828,483
29 transactions · 25 stateful · 2026-08-21 05:42:06 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,828,483 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w19w210w011w112w118w320w021w322w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbee34c12…5fba
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x00096307…5a3d
0x34b655…2a6f
6 touches
3 conflicts
0x5857edf2…dad8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x93aff45d…1722
0x34b655…2a6f
4 touches
1 conflict
0xa93f12a8…c884
0x34b655…2a6f
4 touches
1 conflict
0xaaa40a27…27cd
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
3 conflicts on slot 0xbee34c12c8…555fba
Audit this contract →
← previous block·next block →recent activity