← previous blocknext block →recent activity
Analyzing
Block #97,500,671
14 transactions · 14 stateful · 2026-08-20 01:58:32 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,500,671 · 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
1w03w04w15w18w29w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0099420d…37b4
0x34b655…2a6f
4 touches
1 conflict
0x886f7fe6…8b7a
0x34b655…2a6f
4 touches
1 conflict
0xbd426131…e5d4
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0cbbefe0…7e5f
0x34b655…2a6f
2 touches
0 conflicts
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 0x0099420dea…e337b4
Audit this contract →
← previous block·next block →recent activity