← previous blocknext block →recent activity
Analyzing
Block #86,984,380
21 transactions · 18 stateful · 2026-07-11 04:43:14 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,984,380 · 21 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
1w02w13w04w17w08w110w011w112w114w215w016w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
6 touches
3 conflicts
0x1ef8b4ea…c692
0x065c9d…c394
6 touches
3 conflicts
0x21728e8b…2ab2
0x065c9d…c394
6 touches
3 conflicts
0xa6c0d596…1c34
0x065c9d…c394
5 touches
3 conflicts
0x482f3ed7…3308
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity