← previous blocknext block →recent activity
Analyzing
Block #97,519,818
23 transactions · 23 stateful · 2026-08-20 03:34:52 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,519,818 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w07w18w19w210w015w119w320w421w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c47502…1005
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x21d6593f…26e1
0x34b655…2a6f
4 touches
1 conflict
0x42bebe04…6a3a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0x38c4750210…391005
Audit this contract →
← previous block·next block →recent activity