← previous blocknext block →recent activity
Analyzing
Block #97,501,948
27 transactions · 26 stateful · 2026-08-20 02:04:57 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,501,948 · 27 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
1w02w03w14w05w16w09w110w211w212w216w318w220w325w326w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76ea4d0a…b4b6
0x34b655…2a6f
8 touches
6 conflicts
0x2abb6fec…624a
0xd32edf…ff58
7 touches
6 conflicts
0xef08adcc…6fdf
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x0f94ee4c…1897
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x76ea4d0abb…0ab4b6
Audit this contract →
← previous block·next block →recent activity