← previous blocknext block →recent activity
Analyzing
Block #86,244,564
10 transactions · 9 stateful · 2026-07-07 18:17:17 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,244,564 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dbc306…f976
0x34b655…2a6f
4 touches
1 conflict
0xcda18b0b…6a4c
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x1a9064c9…c8ca
0x34b655…2a6f
4 touches
1 conflict
0x19e0c7c7…2b7a
0x40c49f…2af0
2 touches
0 conflicts
0x1b66cce5…759c
0x40c49f…2af0
2 touches
0 conflicts
0xfa5e306e…c60d
0x40c49f…2af0
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: Perpl
1 conflict on slot 0x59dbc306c4…c6f976
Audit this contract →
← previous block·next block →recent activity