← previous blocknext block →recent activity
Analyzing
Block #97,995,859
49 transactions · 47 stateful · 2026-08-21 19:57:00 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
1.86
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #97,995,859 · 49 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w110w011w112w213w314w415w516w617w718w820w133w234w348w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x81ceb686…4df3
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xf9151634…5de9
0x34b655…2a6f
6 touches
3 conflicts
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: 0xbb3f3cb7…74e046
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity