← previous blocknext block →recent activity
Analyzing
Block #85,214,300
10 transactions · 9 stateful · 2026-07-02 23:49:40 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,214,300 · 10 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
1w02w03w04w15w27w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44564d6…bb43
0x34b655…2a6f
6 touches
3 conflicts
0x1ef30c1e…9a36
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x05a75e4f…8e07
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x89b7ac9a…ceec
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
3 conflicts on slot 0xb44564d6a3…0fbb43
Audit this contract →
← previous block·next block →recent activity