← previous blocknext block →recent activity
Analyzing
Block #97,719,133
31 transactions · 26 stateful · 2026-08-20 20:30:09 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,719,133 · 31 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
2w06w07w110w011w112w117w220w123w228w330w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9db64d13…fb98
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0751c012…af5e
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x7293599a…dbed
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xf0981d44…6ee9
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
6 conflicts on slot 0x9db64d13f5…6efb98
Audit this contract →
← previous block·next block →recent activity