← previous blocknext block →recent activity
Analyzing
Block #97,358,637
14 transactions · 13 stateful · 2026-08-19 13:39:39 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,358,637 · 14 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
4w05w06w17w28w310w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02693e83…54be
0x34b655…2a6f
4 touches
1 conflict
0x0de2686a…2f69
0x34b655…2a6f
4 touches
1 conflict
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x23a89258…d863
0x34b655…2a6f
4 touches
1 conflict
0x388114fc…db6c
0x34b655…2a6f
4 touches
1 conflict
0x388114fc…db6d
0x34b655…2a6f
4 touches
1 conflict
0x47193601…8f8b
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 0x02693e83e4…4154be
Audit this contract →
← previous block·next block →recent activity