← previous blocknext block →recent activity
Analyzing
Block #99,184,597
35 transactions · 23 stateful · 2026-08-26 00:22:04 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,184,597 · 35 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w38w311w418w020w122w224w326w229w330w431w533w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0x3301c4ed…aa52
0x065c9d…c394
5 touches
3 conflicts
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
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
10 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity