← previous blocknext block →recent activity
Analyzing
Block #86,232,586
29 transactions · 23 stateful · 2026-07-07 16:57:15 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,232,586 · 29 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
1w03w04w15w26w09w010w116w318w022w123w425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9086f769…767c
0x065c9d…c394
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd025d7d7…f05a
0x3bd359…433a
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: Market-MON/USDC
6 conflicts on slot 0x9086f76948…fe767c
Audit this contract →
← previous block·next block →recent activity