← previous blocknext block →recent activity
Analyzing
Block #85,200,013
16 transactions · 12 stateful · 2026-07-02 22:14:33 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,200,013 · 16 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
4w05w17w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x833ebd97…5abb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcdc6e1e1…51b2
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x82ac1e5b…6189
0x065c9d…c394
2 touches
0 conflicts
0x91b2f639…9a20
0x065c9d…c394
2 touches
0 conflicts
0xc1dcdf93…5c7b
0x065c9d…c394
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 0x1d6cb7216b…15c88c
Audit this contract →
← previous block·next block →recent activity