← previous blocknext block →recent activity
Analyzing
Block #97,527,989
20 transactions · 20 stateful · 2026-08-20 04:15:58 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,527,989 · 20 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
1w02w03w16w07w19w210w011w112w013w114w216w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x064bb149…79fd
0x34b655…2a6f
4 touches
1 conflict
0x276c8e53…68f1
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x35c37635…11a6
0x34b655…2a6f
4 touches
1 conflict
0x3b5fbc7d…c8fe
0x34b655…2a6f
4 touches
1 conflict
0x454f0656…f9fd
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x5d0cc68b…bcf4
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 0x064bb14971…f579fd
Audit this contract →
← previous block·next block →recent activity