← previous blocknext block →recent activity
Analyzing
Block #97,673,301
40 transactions · 38 stateful · 2026-08-20 16:36:55 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.8
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,673,301 · 40 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w18w09w210w111w312w413w514w615w616w717w819w921w1128w229w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0x40ac662f…df77
0x34b655…2a6f
8 touches
6 conflicts
0xb4a95e21…8ec7
0x34b655…2a6f
6 touches
3 conflicts
0x58e16b8d…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc2108892…2b33
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
15 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity