← previous blocknext block →recent activity
Analyzing
Block #97,509,949
25 transactions · 24 stateful · 2026-08-20 02:45:12 UTC
Parallelism
68/100
Blocked
54%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,509,949 · 25 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
1w03w04w18w09w110w211w312w414w515w616w718w219w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2dcc0868…26bf
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x20c71c23…d507
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xdf0cf99d…47ae
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x1e0cf9b1…e924
0x40c49f…2af0
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
28 conflicts on slot 0x2dcc08681d…0026bf
Audit this contract →
← previous block·next block →recent activity