← previous blocknext block →recent activity
Analyzing
Block #97,614,093
30 transactions · 26 stateful · 2026-08-20 11:32:08 UTC
Parallelism
83/100
Blocked
46%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,614,093 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w08w19w110w211w313w414w015w116w217w119w321w022w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x49e62cd6…7771
0x34b655…2a6f
4 touches
1 conflict
0x69352f9f…5449
0x34b655…2a6f
4 touches
1 conflict
0x73eff9e1…025c
0x34b655…2a6f
4 touches
1 conflict
0x7f38bfbc…61e3
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xba860fcc…24bf
0x34b655…2a6f
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
6 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity