← previous blocknext block →recent activity
Analyzing
Block #97,478,211
21 transactions · 21 stateful · 2026-08-20 00:05:33 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,478,211 · 21 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
2w03w14w05w06w17w28w29w311w312w113w215w416w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1dc86774…166a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x12070f84…331c
0xa6afd3…d132
6 touches
3 conflicts
0xb5e46043…abcd
0xa6afd3…d132
6 touches
3 conflicts
0xda1f3e2c…b73d
0x34b655…2a6f
6 touches
3 conflicts
0x722e8a2a…b7a6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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
10 conflicts on slot 0x1dc86774a8…36166a
Audit this contract →
← previous block·next block →recent activity