← previous blocknext block →recent activity
Analyzing
Block #97,719,255
13 transactions · 13 stateful · 2026-08-20 20:30:45 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,719,255 · 13 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
1w03w04w15w26w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69352f9f…5449
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x101726f8…bf51
0x34b655…2a6f
2 touches
0 conflicts
0x22e35fe3…1f6b
0x34b655…2a6f
2 touches
0 conflicts
0x2b1850ac…fc68
0x34b655…2a6f
2 touches
0 conflicts
0x587be837…f33c
0x34b655…2a6f
2 touches
0 conflicts
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 0x69352f9f62…375449
Audit this contract →
← previous block·next block →recent activity