← previous blocknext block →recent activity
Analyzing
Block #97,187,012
22 transactions · 19 stateful · 2026-08-18 23:08:27 UTC
Parallelism
64/100
Blocked
37%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,187,012 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w111w212w313w414w515w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
14 touches
21 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xc7211c7e…c934
0x851145…3f07
9 touches
10 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0xc72e0b32…21ff
0x851145…3f07
7 touches
6 conflicts
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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: 0x01bff417…bc1071
21 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity