← previous blocknext block →recent activity
Analyzing
Block #97,184,299
34 transactions · 30 stateful · 2026-08-18 22:54:30 UTC
Parallelism
79/100
Blocked
63%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,184,299 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w09w010w111w212w313w414w515w116w619w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0x9fcdf76c…1220
0x851145…3f07
7 touches
6 conflicts
0x86b8fcd1…af85
0x851145…3f07
7 touches
6 conflicts
0xb6b61477…ed3e
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: 0x01bff417…bc1071
15 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity