← previous blocknext block →recent activity
Analyzing
Block #97,397,039
17 transactions · 16 stateful · 2026-08-19 17:15:09 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,397,039 · 17 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
1w03w04w05w16w29w311w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0xc7ed0cd7…a1be
0x34b655…2a6f
6 touches
3 conflicts
0x6f6aa736…a698
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x66767df5…bbde
0x34b655…2a6f
4 touches
1 conflict
0x9a8af3c2…e4ae
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0x48b13e5e9b…6a3c2a
Audit this contract →
← previous block·next block →recent activity