← previous blocknext block →recent activity
Analyzing
Block #97,465,749
26 transactions · 21 stateful · 2026-08-19 23:02:36 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,465,749 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w27w08w09w110w011w115w016w117w219w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22414fbb…1edf
0xa6afd3…d132
4 touches
1 conflict
0x24ad0aca…d5ea
0x40c49f…2af0
4 touches
1 conflict
0x655aa1bb…138c
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x18865c9d…8ced
0xa6afd3…d132
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity