← previous blocknext block →recent activity
Analyzing
Block #85,166,495
17 transactions · 16 stateful · 2026-07-02 18:31:19 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,166,495 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w18w29w310w411w515w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x79563dcc…f82f
0xe52b14…7230
11 touches
15 conflicts
0x3f68ccb5…e301
0xe52b14…7230
4 touches
1 conflict
0x6a3749da…c493
0xe52b14…7230
4 touches
1 conflict
0x6ad5feb6…5606
0xe52b14…7230
4 touches
1 conflict
0xa01610d9…2ed3
0xe52b14…7230
4 touches
1 conflict
0xc4a2f619…eb38
0xe52b14…7230
4 touches
1 conflict
0xef7c06bc…c2eb
0xe52b14…7230
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: 0xe52b1424…bb7230
15 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity