← previous blocknext block →recent activity
Analyzing
Block #97,496,114
19 transactions · 17 stateful · 2026-08-20 01:35:36 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,496,114 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w18w110w111w214w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x516e9b35…57e7
0x34b655…2a6f
6 touches
3 conflicts
0x75c84b81…cf28
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb5e46043…abcd
0xa6afd3…d132
4 touches
1 conflict
0xce163d4f…b563
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x7849d62e…2268
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
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 0x516e9b35e5…8857e7
Audit this contract →
← previous block·next block →recent activity