← previous blocknext block →recent activity
Analyzing
Block #85,578,576
26 transactions · 14 stateful · 2026-07-04 16:15:38 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,578,576 · 26 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
1w02w13w05w114w015w124w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c84e7fe…afbd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x8c0deb70…e86d
0x40c49f…2af0
2 touches
0 conflicts
0xc6119bfd…6187
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 0x8c84e7feff…f2afbd
Audit this contract →
← previous block·next block →recent activity