← previous blocknext block →recent activity
Analyzing
Block #97,356,486
19 transactions · 17 stateful · 2026-08-19 13:28:30 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,356,486 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w08w110w111w012w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b267bdf…b173
0x34b655…2a6f
6 touches
3 conflicts
0x731f2745…9370
0xa6afd3…d132
4 touches
1 conflict
0xbdc0dd06…3e68
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf6ff4f4a…e414
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
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 0x6b267bdfb8…87b173
Audit this contract →
← previous block·next block →recent activity