← previous blocknext block →recent activity
Analyzing
Block #97,668,343
16 transactions · 16 stateful · 2026-08-20 16:11:15 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,668,343 · 16 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
2w03w05w16w210w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a473f81…a214
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0xfcc8f826…7c5f
0x34b655…2a6f
4 touches
1 conflict
0x41be9e75…9773
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x0a473f8155…e5a214
Audit this contract →
← previous block·next block →recent activity