← previous blocknext block →recent activity
Analyzing
Block #85,839,116
16 transactions · 15 stateful · 2026-07-05 21:11:45 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,839,116 · 16 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
8w09w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0xc6f4f168…765c
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2f6e3f9b…cced
0x3c2269…cf62
2 touches
0 conflicts
0x634f554f…186c
0x3c2269…cf62
2 touches
0 conflicts
0x78b6c319…bac0
0x3c2269…cf62
2 touches
0 conflicts
0x81d67c49…e69c
0x3c2269…cf62
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 0x5e782d178d…db5317
Audit this contract →
← previous block·next block →recent activity