← previous blocknext block →recent activity
Analyzing
Block #85,184,320
17 transactions · 16 stateful · 2026-07-02 20:30:04 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,184,320 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9df6ffe0…b995
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x3719925a…83d6
0x34b655…2a6f
2 touches
0 conflicts
0x4b375a43…c6ff
0x34b655…2a6f
2 touches
0 conflicts
0x4d3a9de0…7c14
0x34b655…2a6f
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 0x9df6ffe055…d1b995
Audit this contract →
← previous block·next block →recent activity