← previous blocknext block →recent activity
Analyzing
Block #97,497,253
16 transactions · 14 stateful · 2026-08-20 01:41:20 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,497,253 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8329c51e…4064
0x34b655…2a6f
4 touches
1 conflict
0x886f7fe6…8b7a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xe9662735…4f99
0x34b655…2a6f
4 touches
1 conflict
0xcc8db0c2…8dea
0x34b655…2a6f
3 touches
1 conflict
0x0a1a5467…be4e
0x34b655…2a6f
3 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
1 conflict on slot 0x8329c51ebc…7a4064
Audit this contract →
← previous block·next block →recent activity