← previous blocknext block →recent activity
Analyzing
Block #97,605,283
31 transactions · 26 stateful · 2026-08-20 10:47:19 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,605,283 · 31 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
1w02w04w15w06w17w18w013w214w317w228w029w430w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc9d4fca…ecbf
0x34b655…2a6f
8 touches
6 conflicts
0x99b1f401…7cbf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa5cee576…65ae
0xa6afd3…d132
4 touches
1 conflict
0xc2044b9c…c271
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xcc9d4fcadb…14ecbf
Audit this contract →
← previous block·next block →recent activity