← previous blocknext block →recent activity
Analyzing
Block #97,914,934
13 transactions · 10 stateful · 2026-08-21 13:05:38 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,914,934 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xc91317f3…22e6
0xa6afd3…d132
3 touches
1 conflict
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
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
1 conflict on slot 0xd6bd849ae7…7c5597
Audit this contract →
← previous block·next block →recent activity