← previous blocknext block →recent activity
Analyzing
Block #85,826,968
26 transactions · 18 stateful · 2026-07-05 19:50:52 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,826,968 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w09w110w222w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5681747…c048
0xe1c8b7…3022
6 touches
3 conflicts
0x585836d5…5044
0x9f3832…4ae4
6 touches
3 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
6 touches
3 conflicts
0xd4e43528…777e
0x9f3832…4ae4
6 touches
3 conflicts
0x67d846dd…358c
0xc5db38…7777
6 touches
3 conflicts
0x9527c4ff…73fb
0xc5db38…7777
6 touches
3 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0x1e133356…1a95
0x34b655…2a6f
6 touches
3 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: 0xe1c8b733…e33022
3 conflicts on slot 0xb568174725…c6c048
Audit this contract →
← previous block·next block →recent activity