← previous blocknext block →recent activity
Analyzing
Block #85,103,714
24 transactions · 22 stateful · 2026-07-02 11:32:09 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,103,714 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w19w110w214w015w118w219w320w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x9cf5ac50…1be9
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbaff104b…3edb
0xa6afd3…d132
6 touches
3 conflicts
0x757254ae…d917
0x34b655…2a6f
4 touches
1 conflict
0x7e17e82a…9748
0x34b655…2a6f
4 touches
1 conflict
0xd1a8b9bd…6f8c
0x34b655…2a6f
4 touches
1 conflict
0xd90a674b…29f7
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity