← previous blocknext block →recent activity
Analyzing
Block #85,213,891
34 transactions · 24 stateful · 2026-07-02 23:46:57 UTC
Parallelism
88/100
Blocked
46%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,213,891 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w39w210w317w018w120w023w024w128w029w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb518c12f…4f7f
0xd32edf…ff58
7 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb44564d6…bb43
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xe3ce9025…da31
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity