← previous blocknext block →recent activity
Analyzing
Block #97,467,453
18 transactions · 17 stateful · 2026-08-19 23:11:11 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,467,453 · 18 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
5w06w07w18w19w210w211w312w413w515w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x806c6904…3d63
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xb9716861…8e0a
0x34b655…2a6f
4 touches
1 conflict
0x35c37635…11a6
0x34b655…2a6f
4 touches
1 conflict
0xfd624e64…ef49
0x34b655…2a6f
4 touches
1 conflict
0xa2f71ba7…d3e6
0x34b655…2a6f
4 touches
1 conflict
0xb5f244d5…f550
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
10 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity