← previous blocknext block →recent activity
Analyzing
Block #97,916,078
36 transactions · 26 stateful · 2026-08-21 13:11:32 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,916,078 · 36 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
2w03w110w011w012w013w115w116w218w019w125w126w132w234w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x4d7884af…2e83
0x065c9d…c394
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5eeea918…8147
0x34b655…2a6f
4 touches
1 conflict
0x61ca6437…2142
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x70ea9018…c0e5
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x1125877469…519892
Audit this contract →
← previous block·next block →recent activity