← previous blocknext block →recent activity
Analyzing
Block #86,813,796
19 transactions · 19 stateful · 2026-07-10 09:42:51 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,813,796 · 19 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
1w05w06w17w210w011w312w413w114w015w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0b3a0ce…fc24
0x34b655…2a6f
8 touches
6 conflicts
0xc9eaeefd…d5a3
0x34b655…2a6f
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x9966da31…0d0f
0x34b655…2a6f
6 touches
3 conflicts
0x9f40a209…1193
0x34b655…2a6f
6 touches
3 conflicts
0xd1e5acb9…7b07
0x34b655…2a6f
6 touches
3 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: Perpl
6 conflicts on slot 0xe0b3a0cef4…15fc24
Audit this contract →
← previous block·next block →recent activity