← previous blocknext block →recent activity
Analyzing
Block #87,453,517
16 transactions · 15 stateful · 2026-07-13 09:00:01 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,453,517 · 16 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
1w02w13w24w05w18w29w310w011w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc7a15219…7745
0xa6afd3…d132
6 touches
3 conflicts
0x202c03eb…cf33
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x36810ff7…1728
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb0446875…2b96
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 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity