← previous blocknext block →recent activity
Analyzing
Block #97,357,951
19 transactions · 17 stateful · 2026-08-19 13:36:08 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,357,951 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w013w416w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe54b7d5…1bda
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5d863b2f…bd28
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa85a53e2…0b59
0xd32edf…ff58
3 touches
1 conflict
0xecc59139…b8c9
0xa6afd3…d132
3 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 0xbe54b7d5c9…2a1bda
Audit this contract →
← previous block·next block →recent activity