← previous blocknext block →recent activity
Analyzing
Block #97,842,424
21 transactions · 21 stateful · 2026-08-21 06:52:43 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,842,424 · 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
2w03w04w15w16w27w38w19w210w015w317w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2a2183a…af0b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x2e14aec5…6021
0x34b655…2a6f
4 touches
1 conflict
0x3f4f9f22…8ad6
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0xe2a2183a7c…98af0b
Audit this contract →
← previous block·next block →recent activity