← previous blocknext block →recent activity
Analyzing
Block #97,557,553
17 transactions · 13 stateful · 2026-08-20 06:45:30 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,557,553 · 17 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
1w02w04w15w16w27w38w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e350896…34d8
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x8a06d70a…8ba3
0x34b655…2a6f
4 touches
1 conflict
0x8f505b3d…6aba
0x34b655…2a6f
4 touches
1 conflict
0xb05ec011…f701
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 0x0e3508968e…7d34d8
Audit this contract →
← previous block·next block →recent activity