← previous blocknext block →recent activity
Analyzing
Block #97,556,314
20 transactions · 19 stateful · 2026-08-20 06:39:14 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,556,314 · 20 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
1w02w13w05w06w07w18w19w211w312w415w116w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75fe24d2…46f9
0x34b655…2a6f
6 touches
3 conflicts
0x806c6904…3d63
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00fe3d12…c7d1
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
3 conflicts on slot 0x75fe24d2da…6846f9
Audit this contract →
← previous block·next block →recent activity