← previous blocknext block →recent activity
Analyzing
Block #97,465,451
24 transactions · 21 stateful · 2026-08-19 23:01:06 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,465,451 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w16w27w28w39w410w511w012w217w018w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x806c6904…3d63
0x34b655…2a6f
8 touches
6 conflicts
0xb97c885b…2933
0x34b655…2a6f
6 touches
3 conflicts
0x7c4c9144…17c3
0x34b655…2a6f
4 touches
1 conflict
0x287f71b4…5a6a
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity