← previous blocknext block →recent activity
Analyzing
Block #85,139,343
14 transactions · 12 stateful · 2026-07-02 15:30:33 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,139,343 · 14 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
3w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x353a3a00…5e0a
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x63491cb0…5c0b
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0xa2cc62d4…69f6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0x2406ccf7d1…d8c1cb
Audit this contract →
← previous block·next block →recent activity