← previous blocknext block →recent activity
Analyzing
Block #85,907,267
21 transactions · 17 stateful · 2026-07-06 04:45:48 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,907,267 · 21 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
1w05w18w011w114w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe33d8f47…b271
0x34b655…2a6f
7 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x397501e2…9a12
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x14eedf09…a26f
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
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 0xe33d8f47f0…66b271
Audit this contract →
← previous block·next block →recent activity