← previous blocknext block →recent activity
Analyzing
Block #97,691,019
21 transactions · 20 stateful · 2026-08-20 18:07:15 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,691,019 · 21 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
4w05w06w17w18w09w010w212w013w014w115w116w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247c79f2…e698
0x34b655…2a6f
4 touches
1 conflict
0x2684a9bd…12fa
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x78fb904c…7643
0x34b655…2a6f
4 touches
1 conflict
0x958294fe…2c10
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
1 conflict on slot 0x247c79f2cf…59e698
Audit this contract →
← previous block·next block →recent activity