← previous blocknext block →recent activity
Analyzing
Block #97,559,078
19 transactions · 18 stateful · 2026-08-20 06:53:18 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,559,078 · 19 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
2w04w05w16w17w28w310w415w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x728f999a…832f
0x34b655…2a6f
8 touches
6 conflicts
0x886f7fe6…8b7a
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0x94857e2d…13fc
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac808a27…82db
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 0x728f999afb…4e832f
Audit this contract →
← previous block·next block →recent activity