← previous blocknext block →recent activity
Analyzing
Block #85,631,600
21 transactions · 20 stateful · 2026-07-04 22:08:39 UTC
Parallelism
62/100
Blocked
40%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,631,600 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
16 touches
28 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x036c21d1…e094
0x065c9d…c394
2 touches
0 conflicts
0x5d454752…6230
0x065c9d…c394
2 touches
0 conflicts
0x6321cc3f…fcb3
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0xa8984b63…3562
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: 0x04fdeac2…f747d7
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity