← previous blocknext block →recent activity
Analyzing
Block #97,612,284
19 transactions · 16 stateful · 2026-08-20 11:23:02 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,612,284 · 19 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
1w05w17w010w111w212w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1ee5ec5…4ef0
0x34b655…2a6f
8 touches
6 conflicts
0xba860fcc…24bf
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0xd082cfb3…f9a9
0x34b655…2a6f
4 touches
1 conflict
0xbafc14c9…af82
0x065c9d…c394
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
6 conflicts on slot 0xb1ee5ec564…9e4ef0
Audit this contract →
← previous block·next block →recent activity