← previous blocknext block →recent activity
Analyzing
Block #86,623,824
25 transactions · 16 stateful · 2026-07-09 12:32:51 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,623,824 · 25 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
5w06w18w09w211w116w017w121w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6286219a…0721
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a2
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a4
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x5e47cbde…9659
0x34b655…2a6f
4 touches
1 conflict
0x89c7ec3b…85ba
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity