← previous blocknext block →recent activity
Analyzing
Block #97,397,513
30 transactions · 25 stateful · 2026-08-19 17:17:34 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
1.37
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #97,397,513 · 30 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
1w02w13w05w16w27w28w39w312w413w518w622w926w429w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x178fe051…465a
0x34b655…2a6f
6 touches
3 conflicts
0x984e4d8c…9912
0x34b655…2a6f
6 touches
3 conflicts
0xaab9957c…a4bf
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
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: Perpl
10 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity