← previous blocknext block →recent activity
Analyzing
Block #97,727,095
16 transactions · 16 stateful · 2026-08-20 21:10:28 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,727,095 · 16 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
1w02w04w06w17w18w29w310w411w012w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcb18c96f…8ca8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x8c185f…ec07
4 touches
1 conflict
0x00000000…0008
0x8c185f…ec07
4 touches
1 conflict
0xfc3ae69f…e8da
0x8c185f…ec07
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity