← previous blocknext block →recent activity
Analyzing
Block #86,244,955
13 transactions · 13 stateful · 2026-07-07 18:19:54 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,244,955 · 13 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
2w03w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e9a8e72…7138
0x43cf54…7777
8 touches
6 conflicts
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x59dbc306…f976
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x056e2061…ba40
0x34b655…2a6f
4 touches
1 conflict
0x7bf1c03f…c440
0x34b655…2a6f
2 touches
0 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
2 touches
0 conflicts
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: 0x43cf5407…d87777
6 conflicts on slot 0x1e9a8e7203…ed7138
Audit this contract →
← previous block·next block →recent activity