← previous blocknext block →recent activity
Analyzing
Block #97,465,436
24 transactions · 19 stateful · 2026-08-19 23:01:02 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,465,436 · 24 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
1w06w17w08w19w011w013w114w216w217w319w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0637d14c…1d53
0x34b655…2a6f
6 touches
3 conflicts
0x287f71b4…5a6a
0x34b655…2a6f
6 touches
3 conflicts
0x00d2ebd1…2c24
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5cfec795…7c0e
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d1
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity