← previous blocknext block →recent activity
Analyzing
Block #86,987,833
18 transactions · 16 stateful · 2026-07-11 05:06:19 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,987,833 · 18 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
1w02w13w04w17w08w19w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0178c2de…b37d
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0x74825c4e…32e9
0xb1dbf0…c0d3
6 touches
3 conflicts
0x8d0d8061…d410
0xc8689a…ee79
4 touches
1 conflict
0xc5f336ca…912e
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x6a248bdc…3c1b
0xb1dbf0…c0d3
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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x0178c2de47…64b37d
Audit this contract →
← previous block·next block →recent activity