← previous blocknext block →recent activity
Analyzing
Block #86,384,401
17 transactions · 14 stateful · 2026-07-08 09:51:20 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,384,401 · 17 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
6w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04ed6f3d…7fbe
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xa4e5e0c2…6e04
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x24f29b…4337
2 touches
0 conflicts
0x172b0de5…980b
0x34b655…2a6f
2 touches
0 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x1c96f55b…461e
0x34b655…2a6f
2 touches
0 conflicts
0x3147083e…48d9
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: Perpl
1 conflict on slot 0x04ed6f3d94…987fbe
Audit this contract →
← previous block·next block →recent activity